El Jueves, 3 de Agosto de 2006 09:56, Richard Hobbs escribió: > Hello, > > I have a RH8 server here with 2 identical Maxtor 250GB hard drives. I am > using Soft-RAID to mirror every single partition on these drives (RAID 1). > > This machine does appear to function ok, but i am seeing lots of the > following messages on the console: > > ============================================================ > [root@stg-it2 root]# dmesg | tail -10 > vs-13075: reiserfs_read_inode2: dead inode read from disk [1317 11266 > 0x0 SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1317 10879 > 0x0 SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1317 10879 > 0x0 SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1251 6078 0x0 > SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1317 5380 0x0 > SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1317 8526 0x0 > SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1317 6650 0x0 > SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1251 16144 > 0x0 SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1194 16868 > 0x0 SD]. This is likely to be race with knfsd. Ignore > vs-13075: reiserfs_read_inode2: dead inode read from disk [1251 5222 0x0 > SD]. This is likely to be race with knfsd. Ignore > [root@stg-it2 root]# > ============================================================ > > I have used Maxtor's disk-checking utility, which has certified both > drives as error-free, but these errors continue to appear. > > Can anyone please let me know why this is happening and what can be done > about it? > > Thank you in advance, > Richard. > Messages about read_inode2() ) you see are harmless, so you can safely ignore them. Which kernel are you running? That's a well-known bug of 2.4.18, and it's fixed at linux-2.4.19-pre7, either 2.5 kernels. That warning maybe is due to a file is being deleted by unlink(2). iput() removes inode from hash table and sleeps doing IO truncating file body. On-disk inode (stat-data) is still intact. Last directory entry for this file is already removed. Greetings. -- Manuel Aróstegui Ramírez. Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
