What are the main differences between the current version of 13.1 vs. the future release of 13.2?
What benefits will users experience?
What are the main differences between the current version of 13.1 vs. the future release of 13.2?
What benefits will users experience?
On Mon 05 May 2014 06:36:01 PM CDT, BSDuser wrote:
What are the main differences between the current version of 13.1 vs.
the future release of 13.2?
What benefits will users experience?
Hi
Look at the release announcements?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 05/05/2014 02:45 PM, malcolmlewis wrote:
> https://news.opensuse.org/2014/03/19/development-for-13-2-kicks-off/
>
>The btrfs filesystem is default (and comes with btrfsprogs 3.12)
Finally
–
Bring the Penguins Back! https://features.opensuse.org/316767
openSUSE 13.1
KDE 4.13.0
In the past, btrfs seemed a bit unstable.
Hi
No crashes here with either openSUSE, SLES and SLED, snapper needs tweaking though.
Haven’t had any problems with btrfs, but I question the need for Snapper then to default where btrfs is on the root partition of an average desktop home system, e.g on a notebook or laptop.
The current Snapper defaults (13.1) can easily blow over a 20GB+ partition, unless modified. That relies on users planning and reading openSUSE documentation to avoid running out of system partition space due to aggressive snapshot accumulations by default. Imagine if it came pre-installed with the hardware…
On 2014-05-05 21:36, malcolmlewis wrote:
>
> BSDuser;2641432 Wrote:
>> In the past, btrfs seemed a bit unstable.
> Hi
> No crashes here with either openSUSE, SLES and SLED, snapper needs
> tweaking though.
On 13.1 I managed to reliably crash btrfs, and make the partition
unrecoverable. There is a bugzilla for that, which is not officially
closed, so the issue has not been solved.
>;-)
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On Mon 05 May 2014 11:43:06 PM CDT, Carlos E. R. wrote:
On 2014-05-05 21:36, malcolmlewis wrote:
>
> BSDuser;2641432 Wrote:
>> In the past, btrfs seemed a bit unstable.
> Hi
> No crashes here with either openSUSE, SLES and SLED, snapper needs
> tweaking though.
On 13.1 I managed to reliably crash btrfs, and make the partition
unrecoverable. There is a bugzilla for that, which is not officially
closed, so the issue has not been solved.
>;-)
Hi
Well I guess you won’t like the defaults then… everyone is different
in their use cases, for me I have no issues.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 2014-05-06 02:25, malcolmlewis wrote:
> On Mon 05 May 2014 11:43:06 PM CDT, Carlos E. R. wrote:
>> On 13.1 I managed to reliably crash btrfs, and make the partition
>> unrecoverable. There is a bugzilla for that, which is not officially
>> closed, so the issue has not been solved.
>>
>> >;-)
> Hi
> Well I guess you won’t like the defaults then… everyone is different
> in their use cases, for me I have no issues.
Just try out the test case I used, and find out what happens. Then add a
comment to Bug 846807 saying whether it crashed or not.
What did I do? Well… I simply created one million of 100 byte files on
a 2 GiB btrfs partition. Bizarre? Well, it was just a test, I did not
expect btrfs to crash. None of xfs, ext4, reiserfs… crashed, they just
filled (or not).
The partition was intentionally small in order to stress it more. A
bigger partition would required billions of files, I suppose.
I don’t currently have a factory test system where to try this out, so
if you have one… please test it
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
The version of enlightenment and its packaging will also be improved to be more stable with more packages.
I had problems with Snapper taking up my root partition, back when I installed 13.1 then I found this:
http://www.nrtm.org/index.php/2012/03/13/the-joys-of-btrfs-and-opensuse-or-no-space-left-on-device/
What I did was C & P this from that page.
denkbrett:~ # cat /etc/snapper/configs/root
# subvolume to snapshot
SUBVOLUME="/"
# filesystem type
FSTYPE="btrfs"
# run daily number cleanup
NUMBER_CLEANUP="yes"
# limit for number cleanup
NUMBER_MIN_AGE="1800"
NUMBER_LIMIT="20" # let's only keep 20 snapshots around
# create hourly snapshots
TIMELINE_CREATE="yes"
# cleanup hourly snapshots after some time
TIMELINE_CLEANUP="yes"
# limits for timeline cleanup
TIMELINE_MIN_AGE="1800"
TIMELINE_LIMIT_HOURLY="10"
TIMELINE_LIMIT_DAILY="2" # let's only keep daily snapshots around for two days
TIMELINE_LIMIT_MONTHLY="0" # no I don't want to have things around for 10 months
TIMELINE_LIMIT_YEARLY="0" # or even 10 years! Who came up with those defaults?!?
# cleanup empty pre-post-pairs
EMPTY_PRE_POST_CLEANUP="yes"
# limits for empty pre-post-pair cleanup
EMPTY_PRE_POST_MIN_AGE="1800"
I don’t know how this’ll work for 13.2 but since installation for me on 13.1 it has worked very well.
There is of course openSUSE’s official 13.1 documentation that gets installed on your system, and available on the website . See this page: “Chapter 4. Snapshots/Rollback with Snapper”, in particular section “4.6.1 Adjusting the Config File #”.
Will the defaults be any different for 13.2? I guess we will find out for sure from the later Milestone development releases.
The “missing link” to that web page: Chapter 4. Snapshots/Rollback with Snapper
I can confirm this as I have checked some of your posted hints how you manage btrfs things and “borrowed” them - always good to check forums as somebody brewed a much better solution then myself or save me some time to test various setups.