On 09/16/2013 03:48 PM, Thorsten Kukuk wrote:
On Mon, Sep 16, Sebastian wrote:
i've been using btrfs for over a year now on both root and home with raid1 and compression (whereas /home is on an encrypted lvm), and had several unmountable partitions.
btrfs raid functionality? Hardware raid? mdraid? Sorry, btrfs with raid1 is a little bit to vague. If you mean brtrfs raid functionality: everybody knows that this is unstable and you should not use it, that's why Jeff Mahoney proposed to enable it only with a special command line option.
btrfs raid0/1 is as stable as the rest of btrfs, widely used and well tested (read #btrfs on freenode). btrfs with raid5/6 is unstable and in testing.
moreover, for anything that uses a database (better: has many writes in small portions) like sqlite,
For every database: journaling file systems are always the performance dead for them. There are reasons why people suggest to disable journaling always, even with ext3 and ext4, if you use databases and if you want performance.
the reason here for btrfs is COW. with more and more and more updates it^ll become so fragmented alone reading will take ages.
plus if someone from suse decides to add a "allow_unsupported" switch within initrd, your system becomes unbootable for no reason whatsoever....
That's sound more like you are using the unstable features even kernel developers warns for.
btrfs core is stable, but there are a lot of btrfs features, which are far away from being stable.
the question why that would render MY system unbootable, whereas btrfs would mount without problem, is still unanswered. -- Greetings Sebastian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org