Linked by David Adams on Fri 12th Aug 2011 03:55 UTC, submitted by Debjit
Red Hat The Fedora developers have decided that Fedora 16 will not use Btrfs by default. The announcement was made by Josef Bacik, Senior Software Engineer at Red Hat. Instead the switch to Btrfs filesystem has now been postponed to Fedora 17.
Thread beginning with comment 485030
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by Luminair
by Kebabbert on Mon 15th Aug 2011 09:14 UTC in reply to "RE[2]: Comment by Luminair"
Kebabbert
Member since:
2007-07-27

ZFS is a fine FS that's for sure. As a Linux guy, I have not used myself though and have a question.

About the checksum, if something is not correctly stored on the disk (lets say I save an ODF file), how is the end user informed of the problem? Assuming a hardware problem, what will ZFS do to avoid writing to that sector again? I mean, what is the level of interactivity and robustness of the checksum system to make it useful to say desktop users?

When you type "zpool status" you will see that there are problems. If you are using some kind of raid, then ZFS will detect and repair the problem. If you are using single disk, ZFS will detect the problem, but can not repair the problem.

(Actually, ZFS can also repair errors on single disk too. In effect, everything will be duplicated on the single disk, resulting is halving the storage capacity. You need to specify "copies=2" when you format the single disk for this to happen).

If you see any errors, you should do "fsck" but it is actally called "scrub" instead. And scrubbing data can be performed while you are using your ZFS raid. "fsck" needs to take the raid offline and you have to wait until fsck is done before you can use the raid again.

Here is more information on this:
http://en.wikipedia.org/wiki/ZFS#Data_Integrity

Reply Parent Score: 2