Chris,
Thanks for the report. I think it's possible that this bug and the one
you reported to the jfs-discussion list may be triggered by the same
problem. There seems to be some corruption to the partition's
metadata. The XT_GETPAGE error should have caused the superblock to be
marked dirty, so that on the next reboot, fsck will run completely,
rather than just replaying the journal. This should detect and fix
whatever corruption caused the problem. Let me know if you continue to
see any more traps or syslog errors.
We need to do a bit more "hardening" of the JFS code so that problems
caused by bad on-disk metadata don't cause traps. It would be better
to mark the partition and return an error (where possible).
Determining the cause of the corruption is much harder. If you continue
to see problems, we may be able to determine a repeatable way to create
the problem and get a better idea of what the root cause is.
Thanks,
Shaggy
-- David Kleikamp IBM Linux Technology Center- 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/