btrfs has finally found its way into the latest kernels, is it considered stable and safe enough to use in a home backup scenario (as an alternative to zfs) ?
closed as too localized by xenoterracide♦ Apr 24 '12 at 1:24
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.
|
No, and while fuse-ZFS is the bee's knees (having tried it) I wouldn't use it either. It's not a stability issue - both are fairly stable - but one of code maturity. |
|||||||||||||||
|
|
Novell Suse SLES / SLED 11 support btrfs, so they think it is stable enough for enterprise use. Interesting detail is that they only support readonly ext4. Read/write ext4 is not supported by Novell Suse, forcing enterprise users to use btrfs (or ext3). |
|||
|
|
|
From my /etc/fstab:
So, in a way, yes, it is. I haven't had a single problem with it. However, I reinstall often (I use Fedora, so I install a new release twice a year) and:
my /home is not on btrfs. :) Testing new stuff. It's a dirty job, but somebody has to do it. |
|||
|
|
|
What do you mean by "home backup scenario"? If you mean system that is backuped regulary and you can afford lost of some work ( If you mean fs that underlaying backup you probably need rock-stable filesystem - like ext3/4 with ultra conservative options (Your millage may vary which filesystem). Neither zfs-fuse nor btrfs are stable enough. If you mean that snapshots are your "backup" method - then you have no backup. Probably you should read gotchas and ask youself at each point "can I afford it happening?". |
|||||
|
|
The roadmap for btrfs in Ubuntu is to have it as the default filesystem by 12.04 LTS. The likely cutover to default will be 11.04, other distributions may have more or less aggressive plans, but watching them is your best cue to the perceived stability and reliability and performance of the code. |
|||||||
|