-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/15/2010 09:37 AM, jdd wrote:
Le 15/08/2010 14:30, Matthias G. Eckermann a écrit :
you may read my recent blog about this topic at: http://www.novell.com/communities/node/11736/data-customers-gold
xfs was said, some years ago, to be brillant on very heavy load and random in other. I have no idea what it is now.
I see ext4 very deprecated in your blog. So why was it choosen as default for openSUSE (against ext3)?
The short answer is release schedules. SLES11 is based on openSUSE 11.1, where ext3 was the default. The kernel used was 2.6.27, released in Oct 2008. We could have changed the default for SLE11 since it was released several months after openSUSE 11.1, but I wasn't yet convinced that it was stable enough. openSUSE 11.2 was based on 2.6.31, released 11 months later, which gave ext4 an opportunity to prove itself a little more. Even then, there were expected quirks, like how fsync was needed more frequently, that surprised users. SLES 11 SP1 is based on 2.6.32, so ext4 is pretty stable. The interesting bit here is that between the release of SLES 11 and SLES 11 SP1, btrfs was accepted into the mainline kernel, making it the clear choice for the future. We already support ext3, XFS, reiserfs, and a number of other file systems. The feature gap that ext4 filled was already filled in SLES by XFS for a number of years already, so we chose not to support it.
Do you have links on the room used by btrfs (~= journal size). I know reiser was at least 50Mo, so not good for small partitions (for /boot, for example). xfs uses less room what about btrfs? looks like btrfs is more a disk manager than a filesystem manager
Btrfs doesn't use a journal at all. The overhead of a brand new btrfs file system is quite small. The bit that complicates things is that it is a log based file system (different than journal!) and operates by being copy-on-write to the core. New writes are written and then linked into the tree atomically. With the exception of the superblock (I think), there are no places in btrfs where a block contains data that must be continually updated. This also means, ironically, that you need free space to delete things.
what is the *windows* situation about btrfs? Having a native windows driver for our file system (like ext3ifs for ext3) is very important relative as default install, often dualboot for rendom user
AFAIK there is no Windows support at all. I'd hazard a guess that the number of users sharing data between Linux and Windows *and* are using a Linux-based file system to do it are probably a very small minority. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkxomGMACgkQLPWxlyuTD7KI2QCdEf2+MZo1aZ/DOz42iZ8DmWjD odUAn0zUPhQvzaNXvpx4m4ksV9gJjimG =UM1i -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org