> From: Dave Kleikamp <sha...@li...> - 2009-04-02 12:46 > > You seem to be using jfs_fsck correctly, but it's finding something it > can't handle. I don't know why it was written this way, but jfs_fsck > likes to find all the errors first and then fix them all at the end. > Unfortunately, something is preventing it from finishing. > > rc=-268 in phase 0 indicates that the journal superblock is > unrecognized. This could mean that a large part of the volume could be > corrupted. Could this be caused by a RAID problem, such as a disk going > offline?
The server lost power unexpectedly. The drives are managed by a hardware RAID, but it's reporting that all of the drives are fine. > I think exit code 134 means that the program was killed by a SIGABRT > signal. I'm not sure where that's coming from. Is there anything at > the end of the output that gives a clue? Is there anything unusual in > the syslog? Syslog shows nothing. The last few lines of output show: The path(s) refer to an unallocated file. Will remove. File system object FF1564740 is linked as: modules/metanet/macros/graph_tools/2.122e-314raph_p.sci File system object FF1564740 is linked as: macros/graph_tools/2.122e-314raph_p.sci The path(s) refer to an unallocated file. Will remove. *** %n in writable segment detected *** File system object FF1564741 is linked as: modules/metanet/macros/graph_tools/Aborted Michael ------------------------------------------------------------------------------ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
