On Tuesday 09 July 2002 05:23, Bernhard Mogens Ege wrote: > 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?
Unfortunately, fsck.jfs does not currently fix the problem leading to the find_entry errors. However, these warnings should only lead to problems reading and accessing entries in the directory, and should not cause further problems. > 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). Are these errors similar to the ones reported in your last message? Those error messages indicated massive filesystem corruption, as if entire portions of the partition where corrupted. I'm not aware of any other reported problems that indicate this kind of problem. I can try to stress JFS under NFS. I haven't played with NFS in a while. I assume you're using NFSv3? What kind of workload is being run on the clients? -- David Kleikamp IBM Linux Technology Center _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
