Pottential Problem

[Justin Thomas]

I've been receiving messages in my logs regarding a reiserfs partition I 
have on my system.  At first, I thought that one of my drives was going 
bad, so I really didn't pay it much attention.  Now that I look closer, 
however, I notice this:

Feb 26 00:02:39 JTLinux kernel: hdb: drive not ready for command
Feb 26 00:02:52 JTLinux kernel: hdb: lost interrupt
Feb 26 00:02:53 JTLinux kernel: hdb: status error: status=0x58 { 
DriveReady SeekComplete DataRequest }
Feb 26 00:02:53 JTLinux kernel: hdb: drive not ready for command
Feb 26 00:02:54 JTLinux kernel: attempt to access beyond end of device
Feb 26 00:02:54 JTLinux kernel: 03:41: rw=0, want=584642676, limit=8255488
Feb 26 00:02:54 JTLinux kernel: attempt to access beyond end of device
Feb 26 00:03:05 JTLinux kernel: 03:41: rw=0, want=596901940, limit=8255488
Feb 26 00:03:05 JTLinux kernel: attempt to access beyond end of device
Feb 26 00:03:05 JTLinux kernel: 03:41: rw=0, want=584642676, limit=8255488
. . . These messages are repeated a whole lot . . 
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Feb 26 00:06:07 JTLinux kernel: hdb: lost interrupt
Feb 26 00:06:08 JTLinux kernel: is_tree_node: node level 30742 does not 
match to the expected one 1
Feb 26 00:06:08 JTLinux kernel: vs-5150: search_by_key: invalid format 
found in block 8899. Fsck?
Feb 26 00:06:08 JTLinux kernel: vs-13070: reiserfs_read_inode2: i/o 
failure occurred trying to find stat data of [10 168 0x0 SD]
Feb 26 00:06:08 JTLinux kernel: vs-13048: reiserfs_iget: bad_inode. Stat 
data of (10 168) not found
Feb 26 00:06:08 JTLinux last message repeated 5 times
Feb 26 00:06:08 JTLinux kernel: hdb: status error: status=0x58 { 
DriveReady SeekComplete DataRequest }
Feb 26 00:06:08 JTLinux kernel: hdb: drive not ready for command
Feb 26 00:06:08 JTLinux kernel: is_tree_node: node level 30742 does not 
match to the expected one 1
Feb 26 00:06:08 JTLinux kernel: vs-5150: search_by_key: invalid format 
found in block 8899. Fsck?
Feb 26 00:06:08 JTLinux kernel: vs-13070: reiserfs_read_inode2: i/o 
failure occurred trying to find stat data of [10 169 0x0 SD]
Feb 26 00:06:08 JTLinux kernel: vs-13048: reiserfs_iget: bad_inode. Stat 
data of (10 169) not found
Feb 26 00:06:08 JTLinux last message repeated 5 times
Feb 26 00:06:08 JTLinux kernel: is_tree_node: node level 30742 does not 
match to the expected one 1
Feb 26 00:06:08 JTLinux kernel: vs-5150: search_by_key: invalid format 
found in block 8899. Fsck?
Feb 26 00:06:09 JTLinux kernel: vs-13070: reiserfs_read_inode2: i/o 
failure occurred trying to find stat data of [10 170 0x0 SD]
Feb 26 00:06:09 JTLinux kernel: vs-13048: reiserfs_iget: bad_inode. Stat 
data of (10 170) not found
_________________

Now, the statement that says: want=596901940, limit=8255488 worries me.  
This is an 8.4gig Western Digital drive, so the number, 8255488 seems 
reasonable enough.  The number 596901940 seems totally unreasonable.  Do 
you think I am looking at a hardware problem, or do you think it could 
be kernel related?  I am using kernel 2.4.1 on a SuSE Linux 7.0 system.

Thanks in advance,
Justin