Andrew, for future reference, a much simpler way of debugging this
sort of problem (which doesn't require interpreting od -x dumps) is to
ask the user to use the command:
dumpe2fs -f -h /dev/hdd1
To clear the feature flag, you can use the debugfs program:
% debugfs
debugfs: open -w -f /tmp/testfs
debugfs: features
Filesystem features: filetype FEATURE_I16 sparse_super
debugfs: feature ^feature_i16
debugfs: features
Filesystem features: filetype sparse_super
debugfs: quit
> I managed to fix it by running e2fsck off one of the backup
> superblocks - that seems to have repaired the broken bits:
> Then I just reran "tune2fs -j", and mounted it as ext3. I hope that
> was the correct approach, but its working in any case :) Don't quite
> know why/how the superblock got corrupted like that in the first
> place :-/
Well, sounds like the in-core copy of the superblock got corrupted
somehow, or perhaps a passing bit of cosmic radiation flipped the bit
as it was getting written back to disk. If you can get it to do it
repeatably it, or if it even happens once or twice more, we'd
definitely want to know more about it.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:31 EST