Date: Tue, 11 Apr 2000 11:58:55 -0700 (PDT)
From: Andre Hedrick <andre@linux-ide.org>
You mentioned that there is no way to actively update the badblocks list
in EXT2. Can you explain or tell me how I can kludge around this?
Also will EXT3 have this as a native feature?
You can update it using e2fsck's -c, -l, or -L options.
When the kernel detects a bad block, it's not so simple to just throw it
into the badblocks list --- the block may very well likely be in use as
filesystem metadata, or because it's in use as a file data block. It
might be possible to have the kernel handle more of these cases
automatically without requiring an fsck, but past a certain point,
you're introducing *way* to much hair into the kernel.
I know, I know, Multics did have the ability to do on-line filesystem
scavaging, which basically when all of what we would call e2fsck
(including a garbage collector because directories were a minature LISP
world) was in the kernel. I however, am not sure we want to go there. :-)
- Ted
-
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:16 EST