Hi,
On Wed, Apr 12, 2000 at 01:46:33AM -0400, Theodore Y. Ts'o wrote:
>
> As far as what the filesystem can do, in *some* cases it may be able to
> put the block onto the bad block, and then retry the write, but in other
> cases, where the filesystem was just reading from a pre-existing file,
> there really isn't much the filesystem can do that's sane. It could
> unlink the block from the inode, and leave a hole there, and then relink
> the block to the bad-block inode, but underlying applications still
> probably won't deal well with that happening.
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.
--Stephen
-
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