I had an NFS file server using JFS fail this weekend. A reboot, which made fsck do a full check, seems to have cleared everything up. The initial errors I got were:
Jun 25 09:27:04 nicfs2 kernel: Incorrect number of segments after building list Jun 25 09:27:04 nicfs2 kernel: counted 16, received 15 Jun 25 09:27:04 nicfs2 kernel: req nr_sec 320, cur_nr_sec 8 Jun 25 09:27:04 nicfs2 kernel: device-mapper: dm-multipath: Failing path 8:96. Jun 25 09:27:04 nicfs2 kernel: cfq: depth 4 reached, tagging now on Jun 25 09:27:04 nicfs2 kernel: end_request: I/O error, dev sdc, sector 1592060824 Jun 25 09:27:04 nicfs2 kernel: device-mapper: dm-multipath: Failing path 8:32. Jun 25 09:27:04 nicfs2 kernel: end_request: I/O error, dev sdc, sector 1592062936 Following that was a flurry of JFS errors. I assume these messages have nothing at all to do with JFS, but I wanted to make certain. I can't turn up much googling that error. If anyone has any idea what caused that I'd love to hear it. One last question, for an NFS server is it better to mount the volume with errors=panic? It seems like that would keep I/Os from failing due to it being a read-only file system on error. In this case it would seem like a panic + boot would have let a lot of processes (this is used in a batch environment) resume. Chris ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
