-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LNX.2.00.1310021638120.1095@Telcontar.valinor> On Wednesday, 2013-10-02 at 09:34 -0400, Anton Aylward wrote:
Greg Freemyer said the following on 10/02/2013 08:35 AM:
Apart from a small swap partition the whole of the disk is one huge great BtrFS partition. There is no separate /boot. All of /var/ /usr /home are in the one huge partition. I figured if BtrFS can optimise then let it optimise the hell out of things :-)
The issue with one partition of any type (no /home) is that you can not reinstall the system, typically with a new release, because it means reformatting home and loosing your data.
It works read good, I've had no disappointments.
Yes fsck is missing but I've had no problems.
And if you do have a problem, how will you do an fsck on it? That's the question. Eventually, now, in ten years, you will need it.
The issue is limited links (hard? / soft?).
I have.
I've never heard of that, can you give references please?
+++································ Date: Wed, 04 Sep 2013 12:04:58 -0400 From: Jeff Mahoney <**@suse.com> To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Re: BtrFS as default fs? - - Removal of the strange per-directory hard link limit - Due to the backreferences to a single inode needing to fit in a single file system block, there was a limit to the number of hard links in a single directory. It could be quite low. - Limit removed by adding a new extended inode ref item, not enabled by default yet since it's a disk format change. Extended inode ref only used when required since it's not as space-efficient as the single node item. There's probably room for discussion within the file system community on whether we'd want to add an "ok to change" bit so that file systems have the ability to use the new extended inode ref items when needed but doesn't set the incompat bit until they're actually used. The other side of that coin is that it may not be clear to users when/if their file system has become incompatible with older kernels. ································++- Notice that the improvement needs reformat of the partition.
There is serious discussion on factory of declaring a subset of the btrfs features stable for root usage with 13.1 due out next month.
The issue with BtrFS isn't simply stable/unstable as a binary choice so much as, well I keep pointing out
There are features of btrfs that will be deactivated by default on 13.1, like for example, filessystem compression, because *the devs* do not think it is stable enough.
and the issue is "are you going to be operating in one of the unstable areas?"
I would. Compression is precissely the feature I want.
My desktop: browsing; email; some documentation; reading PDF papers; some photo editing; playing a bit of music - nothing very extreme or stressing. Typical desktop for many 'home users'. No problems with BtrFS.
In that same factory thread there was a link to a speed test of several fileystems, and btrfs was the slowest on some of the tests.
And by the way, please can I have the references to the apps that won't load and the mention of running out of links/inodes with BtrFS. Failing that I'm going to consider them unsubstantiated malicious rumours.
+++································ Date: Thu, 05 Sep 2013 11:42:08 +0200 From: Stephan Kulow <***@suse.de> To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] BtrFS as default fs? At the moment you can't even install factory with btfs as default because of bugs as bnc#835695 ································++- +++································ The bug *is* fixed - https://build.opensuse.org/request/show/198042 And yes, yast should have given an error dialog about the problem - still that the error is there is btrfs' fault. But that problem is fixed too - it's still a problem on updates though. We need to make sure not to use too many hardlinks not to break zypper dups from 12.3 on btrfs. ································++- Read that thread, a lot of issues are discussed.
And as for ReiserFS, don't let the fact that the original designer is jailed for murder. This is a damn good FS and there have been no serious problems with it recently. Its a great example of getting things tight the first time instead of needing to constantly tweak and hack. Compare, with Internet Explorer :-)
You can no longer install openSUSE with it, as it has been removed from the install disk partitioner (13.1) - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJMMDcACgkQtTMYHG2NR9UwSwCdGMQdp7aY5iD8iy3uJo9X/BBA LPcAnjfNduGU0TMsAswnuRvW18VxbUgC =jmKn -----END PGP SIGNATURE-----