On Tue, Nov 29, 2011 at 13:19, C <smaug42@opensuse.org> wrote:
On Tue, Nov 29, 2011 at 13:10, Martin Helm <martin@mhelm.de> wrote:
"Note that Btrfs does not yet have a fsck tool that can fix errors. While Btrfs is stable on a stable machine, it is currently possible to corrupt a filesystem irrecoverably if your machine crashes or loses power on disks that don't handle flush requests correctly. This will be fixed when the fsck tool is ready."
Can the "disks that don't handle flush requests correctly" be clarified a bit? Does this apply to most disks? A small subset of disks? Just how high is the risk here?
Just replying to myself here with a bit more information on this... when you look here: https://btrfs.wiki.kernel.org/articles/f/a/q/FAQ_1fe9.html#Is_btrfs_stable.3... There is an interesting and possibly helpful comment on possible BTRFS corruption : "the vast majority of the problems with broken and unmountable filesystems I've seen on IRC and the mailing list have been caused by power outages in the middle of a write to the FS, and have been fixable by use of the btrfs-zero-log tool." Would it be useful to digest this into something in the Release Notes as well? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org