e2fsck -c did not work FWIW....
But I've found a bug in e2fsck:
If a bad block is in a spot occupied by a superblock backup,
ext2 programs crash (fsck particularily).
Is there anything that can be done about this?
Or am I the first one to have a shipping defect right where Linux likes to
put one of the superblock backups?
Err, no, e2fsck shouldn't be crashing; and the transcripts which you
sent me yesterday (sorry for not responding right away, but I've been
rather busy lately), don't show anything of the sort. The problem you
had was that a block appeared both on the the bad blocks list and on the
bad blocks indirect block. That's a very different thing.
I'll send you some more mail in private, but basically I'm going to need
complete transcripts of mke2fs (assuming that you were running e2fsck on
a freshly made filesystem, which is not at all clear), and e2fsck, and
descriptions of the filesystem state beforehand if it was not a freshly
made filesystem.
Pet peeve --- people, please think a bit about how to send in a complete
bug report. DON'T leap to conclusions, or at the very least, if you
must theorize, give me full data and full information that led you to
believe what you believe. Full transcripts of everything and full
descriptions of your hardware and what you observed, is far more useful
than your conclusions.
If it's any incentive, messages which don't have full and complete
information typically don't get answered right away, because it's more
effort to explain to the user why his conclusion was in space, or at
least not even vaguely supported with the data that he deigned to
supply, and to start specifying all the data that I would need.
Messages which do give me the full and complete information generally
get responded to right away, because usually those are much easier to
answer. (And nine times out of ten it's operator error, or the user
having an outdated version of e2fsck.)
- Ted