On Wed, Apr 12, 2000 at 10:34:39AM +0100, Stephen C. Tweedie wrote:
> 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.
What about a 'soft' bad blocks list? The filesystem could remember
bad blocks in a seperate list, and can avoid this blocks if it has
a choice, for example for new allocations.
Additionally, e2fsck could use this list on the next reboot and add
it to the real bad block list, relocating existing data if needed
(and possible).
By the way, what's the state of ext3 with 2.3.* kernels? Are there
any patches available?
Jan
-
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:18 EST