> While I cannot help with explaining the fsck output, but: what has lead to > these corruptions in the first place? power outage? hardware failures? If > the latter, were they fixed?
Yes there was a power outage. The system is setup to always do a fsck.jfs on the volume upon boot and that's probably when 37 of these read errors occurred consecutively to the device : Jun 14 19:23:02 system ERROR: (device dm-5): diRead: i_ino != di_number I wasn't around to check up on what happened until yesterday :( . > Oh, and if you can: try fsck on a backup first, with LVM I guess a > readonly snapshot should do. This way you can always revert to the > "original corruption". Unfortunately snapshotting was never setup on this LVM. ------------------------------------------------------------------------------ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
