Why SUSE Likes The Btrfs File-System
Phoronix: Why SUSE Likes The Btrfs File-System
While many assumed Fedora would be the first tier-one Linux distribution shipping with Btrfs by default, it looks like openSUSE may end up being the one. OpenSUSE has been looking at switching to Btrfs for their next release (post-13.1) and already in its current state feel Btrfs is safe for users -- nearly one year after SUSE Enterprise felt Btrfs is production-ready...
Would be really nice to see these snapshotting capabilities of Btrfs come to Debian (apt, apt-get, synaptic, aptitude) too...
We've been running btrfs on multiple systems (desktops and server) in multiple configurations (single, raid0, raid1). After 15 months, we haven't encountered any issues.
I think where people get into trouble with btrfs is that if their system experiences a problem (e.g., power outage), their first thought is to run btrfsck. However, btrfsck is the last thing you should try. The first thing is to just let btrfs resolve any issues on its own; much of the fsck functionality occurs at mount. If that doesn't work, mount with the '-o recovery' option. That lets btrfs go back in time, trying previous filesystem tree roots until it finds one with integrity. You may lose the last few seconds of changes, but your data will be intact.
In fact, btrfs saved me when an external drive was silently corrupting data (hardware fail). Since btrfs checksums data blocks, it reported the issue. SMART indicated no problem with the drive, but in fact it was writing trash. I previously had EXT4 on the drive, and it was silent. The backups I was writing to it were worthless, but until I converted to btrfs I didn't know there was an issue.
I guess there's no surprise that the ZFS advocates are banding together under OpenZFS and also try to push ZFS onto Linux through efforts like ZFSOnLinux.
BTRFS is arriving now and it has the huge advantage of being shipped and maintained directly in the Linux kernel which means it will likely quickly become the de facto default file system on Linux once it has been tested in the wild (like here with SUSE), which in turn means there will be a lot more developer resources allocated towards BTRFS as all the companies which rely on Linux will want to get the best performance/features out of it.
Meanwhile the open source ZFS implementation which due to licence means can't be included in the kernel has been cut off from 'upstream' enhancements from Oracle as they no longer open source them, leaving the open ZFS effort without any real commercial backing from what I can see.
This likely means that it will struggle against BTRFS feature-wise in the long run, and since BTRFS is shipped with the kernel I can't see ZFS getting any real foothold on Linux once BTRFS is shipped as default with most distros.
So they need to act now and try to make it as painless as possible to use ZFS on Linux, which I think is what they are trying to do with ZFSOnLinux.
I don't think it will work though. The advantage of being able to be shipped in the kernel is just too big, so I believe BTRFS will become the standard on Linux and ZFS will remain largely confined to the BSD's with little to no Linux presence to speak of.
Feel free to do that. I made an ebuild of Snapper for Gentoo, for instance.
Originally Posted by uid313
So does BTRFS has some kind of fsck, yet?
Yes, but odds are you don't want to use it; it's not EXT4. See comment #3.
Originally Posted by blackout23
I am not using it until it has FSCK, Duke Nukem Forever is released, Steam is ported to Linux and Microsoft submits patches to the kernel.
So, you've been using btrfs for about a month now?
Originally Posted by ssam
yes. Actually quite a lot longer. :-)
Originally Posted by macemoneta