On Fri, 2007-12-14 at 10:09 +0100, Mika wrote: > Hi, > > I got a couple of the following errors on my JFS partition, which resulted > in the partition marked as dirty and remounted read only: > > ERROR: (device dm-0): diRead: i_ino != di_number > > Around the same time I got some strange memory errors from the kernel, > 2.6.22.9. I googled a bit and this seems to have been a bug. Is that still > the case?
There was an earlier report of this, but I never got enough information to determine what caused it. > There was no info on the bugtracker that I could see. I don't think anyone opened a bug against it. > I ran jfs_fsck and > it reported some errors that it corrected, and I could remount the partition. > > I have not seen these kind of problems on machines that hasn't crashed with > other filesystems, like RiserFS/Ext3/FFS and so, unless there really is a > hardware failure. Possibly. Or a kernel bug somewhere else besides jfs. Could I have some more information? The earlier report was with a file system on top of RAID5 and nfs running on top of it. It could be that jfs isn't playing nicely with one or the other. Was this an SMP machine? > I previously ran ReiserFS on that partition, but with a > disk change i switched to JFS, just for testing. But if I keep get > corrupted filesystems on a running system I will switch back to ReiserFS, > which ran perfectly for a couple of years. Please let me know if you do see it again. Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
