>>>>> "Bernhard" == Bernhard Mogens Ege <[EMAIL PROTECTED]> writes:
>> If you have any entries in lost+found, these are created without the cookie >> table. (We need to fix this.) If that's not the case, I'm not aware of >> any known problems resulting in this condition. > We do not have entries in lost+found and JFS is constantly producing > error messages in our system log. Newer JFS versions produce more > errors (and crashes more often) then earlier versions. > We have run a series of tests on our system, but none have been able > to conclude that we have hardware failure. We have even run a low > level SCSI test (from the stress-kernel package) that did not reveal > any problems. > The JFS partition is located on a Mylex DAC960 Raid 5 array and shared > via NFS (smp setup). Is anyone else using a similar configuration > succesfully? We have just replaced our Raid controller with a new one, expecting the errors to subside, but they keep coming: Jul 9 02:48:57 boston kernel: find_entry called with index = 0 Jul 9 04:02:22 boston kernel: find_entry called with index = 0 We did a full fsck after the installation of the new raid controller, and we now believe our problems are JFS related. I guess JFS just isn't NFS friendly enough yet (as written in the FAQ. Should we switch filesystem or could we perform additional tests? The above log entries are usually followed up by numerous other JFS errors after a while and then the server crashes (after at most 5-7 days with the newest JFS/kernel release). regards, Bernhard Ege _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
