"Theodore Y. Ts'o" wrote:
>
> Date: Wed, 12 Apr 2000 10:34:39 +0100
> From: "Stephen C. Tweedie" <sct@redhat.com>
>
> Right now it's really not practical to do any of that except for
> synchronous writes, because the filesystem has no way of knowing
> what file a given block belongs to in general. The only way
> e2fsck can work that out is to scan the whole filesystem looking
> for the ownership of the bad block.
>
> Oh, if we were going to do this we'd have to add tags to the buffer
> structure to indicate the inode number and logical block number, so that
> if a buffer gets returned with an error, the filesystem can figure out
> what to do with it. (Which in the case of filesystem metadata still
> could be nothing but the current choice of ignore the error, panic, or
> mark the filesystem as read-only.)
>
> - Ted
if you tagged the buffer with the inode reference you would also
have an easy way to improve ext2's fsync performance.
jan-simon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:19 EST