On Sat, 2005-11-26 at 21:52 +0100, szonyi calin wrote: > Hello > > With 2.6.14.1 kernel (from kernel.org - no other patches) i > found the following error: > > Nov 22 20:42:41 grinch kernel: ERROR: (device hda6): diRead: > i_ino != di_number > > Nov 26 20:45:41 grinch kernel: ERROR: (device hda8): diRead: > i_ino != di_number > > I guess this errors are appearing when i run slocate because > slocate is running at 20:40 every day.
It seems reasonable that you would see the error then, but the inode was probably messed up some time earlier. I don't know of any known bugs to explain it though. :-( > After reboot fsck says that it deleted a file from the > filesystem on which the error occured. I didn't save fsck > output. Are these the same filesystem (hda6 & hda8)? Let me know if you see a similar problem again, as fsck should have fixed the problem this time. > The filesystems were over 90% full when this happened. > > Bye > Calin -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
