On Thu, 2008-08-07 at 11:14 +0200, Peter Zijlstra wrote: > On Tue, 2008-08-05 at 15:01 -0400, Chris Mason wrote: > > > There are still more disk format changes planned, but we're making every > > effort to get them out of the way as quickly as we can. You can see the > > major features we have planned on the development timeline: > > > > http://btrfs.wiki.kernel.org/index.php/Development_timeline > > Just took a peek, seems to be slightly out of date as it still lists the > single mutex thingy. Thanks, I thought I had removed all the references to it on that page, but there was one left. > > Also, how true is the IO-error and disk-full claim? > We still don't handle disk full. The IO errors are handled most of the time. If a checksum doesn't match or the lower layers report an IO error, btrfs will use an alternate mirror of the block. If there is no alternate mirror, the caller gets EIO and in the case of a failed csum, the page is zero filled (actually filled with ones so I can find bogus pages in an oops). Metadata is duplicated by default even on single spindle drives, so this means that metadata IO errors are handled as long as the other mirror is happy. If mirroring is off or both mirrors are bad, we currently get into trouble. data pages work better, those errors bubble up to userland just like in other filesystems. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
