Valerie Henson wrote: > On Jan 8, 2008 8:40 PM, Al Boldi <[EMAIL PROTECTED]> wrote: > > Rik van Riel wrote: > > > Al Boldi <[EMAIL PROTECTED]> wrote: > > > > Has there been some thought about an incremental fsck? > > > > > > > > You know, somehow fencing a sub-dir to do an online fsck? > > > > > > Search for "chunkfs" > > > > Sure, and there is TileFS too. > > > > But why wouldn't it be possible to do this on the current fs > > infrastructure, using just a smart fsck, working incrementally on some > > sub-dir? > > Several data structures are file system wide and require finding every > allocated file and block to check that they are correct. In > particular, block and inode bitmaps can't be checked per subdirectory.
Ok, but let's look at this a bit more opportunistic / optimistic. Even after a black-out shutdown, the corruption is pretty minimal, using ext3fs at least. So let's take advantage of this fact and do an optimistic fsck, to assure integrity per-dir, and assume no external corruption. Then we release this checked dir to the wild (optionally ro), and check the next. Once we find external inconsistencies we either fix it unconditionally, based on some preconfigured actions, or present the user with options. All this could be per-dir or using some form of on-the-fly file-block-zoning. And there probably is a lot more to it, but it should conceptually be possible, with more thoughts though... > http://infohost.nmt.edu/~val/review/chunkfs.pdf Thanks! -- Al - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
