On Wednesday 02 April 2003 13:31, Chris Stromsoe wrote: > A decoded oops report, the output from /proc/fs/jfs/*, and the > ver_linux output is included below. The kernel is stock 2.4.20 with > JFS 1.1.2 from http://oss.software.ibm.com/jfs/ > > > -Chris
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 _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
