Excerpts from Andi Kleen's message of 2011-07-02 13:04:43 -0400: > > The two big features of btrfs are self-healing and online fsck, those have > > to > > Are they? > > > be implemented in kernel space. > > Why? There have been online fscks in user space in the past, > e.g. the various schemes using LVM snapshots for ext* and > other related work on the BSD FFS. I don't see any principal > reason why it couldn't be done for btrfs either. > > A good fsck is quite complex and you are unlikely to want all > that code in kernel space.
The offline fsck for btrfs is basically for repairing the worst possible problems (things that make the FS unmountable). The online code can easily take on smaller things, like detecting incorrect link counts and a whole series of other problems that shouldn't require offline access. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
