Error message - vs-13070

Error message - vs-13070

[Andrew Heberle]

Twice in the last four days I have found the following message in one of my 
systems logs:

vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat 
data of [1718696 1718710 0x0 SD]

I have managed to track this error back to a particular file.

When attempting an 'ls' on the file in question I get a "Permission denied" 
message.

The error suggests a bad block on the hard drive where that file exists I 
assume?

I have yet to run reiserfsck on the machine as it is well backed-up, 
working fine at the moment (the file in question is only ever touched 
during updates of the slocate database), and I can't take it down to run 
reiserfsck at the moment anyway (the error is on the root partition).

I suppose I am just wanting confirmation that based on the error message 
this is likely to be a hardware issure rather than being caused by an 
as-yet unknown corruption bug in reiserfs (I find this very unlikely based 
on my past, very stable history with reiserfs).

--
Andrew Heberle

Re: Error message - vs-13070

[Oleg Drokin]

Hello!

On Sat, Feb 15, 2003 at 12:26:53AM +0800, Andrew Heberle wrote:

> Twice in the last four days I have found the following message in one of my 
> systems logs:
> vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat 
> data of [1718696 1718710 0x0 SD]
> I have managed to track this error back to a particular file.
> When attempting an 'ls' on the file in question I get a "Permission denied" 
> message.

What kernel is that?
Were there any other messages around this one in logs? (not necessary reiserfs
related)

> The error suggests a bad block on the hard drive where that file exists I 
> assume?

There is some I/O error (including but not limited to bad sectors, corrupted
filesystem nodes, corrupted tree consistency and so on).
The reason for it should be explained by other messages that should appear in
your logs just before this message.

> I suppose I am just wanting confirmation that based on the error message 
> this is likely to be a hardware issure rather than being caused by an 
> as-yet unknown corruption bug in reiserfs (I find this very unlikely based 
> on my past, very stable history with reiserfs).

We cannot tell without those extra messages.
You can execute 'dmesg' and find out what is there in addition to
those vs-13070

Bye,
    Oleg

Re: Error message - vs-13070

[Andrew Heberle]

>What kernel is that?
>Were there any other messages around this one in logs? (not necessary reiserfs
>related)

It is the latest gentoo-sources kernel, which is based on 2.4.19 I think, 
although Gentoo kernel's
have a number of extras added in them, along with a number of fixes not 
found in the mainline kernel.


>We cannot tell without those extra messages.
>You can execute 'dmesg' and find out what is there in addition to
>those vs-13070

The following errors show up in the kernel logs at the time:

hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6599945, 
sector=4286584
end_request: I/O error, dev 03:03 (hda), sector 4286584

These errors look to me like a hardware problem (bad sector on the drive).

Definately not a reiserfs problem, thanks for the reply Oleg.

--
Andrew Heberle

Re: Error message - vs-13070

[Todd Lyons]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew Heberle wanted us to know:

>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6599945, 
>sector=4286584
>end_request: I/O error, dev 03:03 (hda), sector 4286584
>These errors look to me like a hardware problem (bad sector on the drive).
>Definately not a reiserfs problem, thanks for the reply Oleg.

Depends, is 4286584 beyond the end of what really exists, or is that in
the middle of your valid sectors?
- -- 
Blue skies...	Todd 	Public key: http://www.mrball.net/todd.asc
We're sysadmins.  To us, data is a protocol overhead.  --Mans Nilsson
   Linux kernel 2.4.19-16mdk   3 users,  load average: 0.00, 0.00, 0.00
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+T69nIBT1264ScBURApNeAJ9jkcgnpp3MPQSG0epvnNpuLdLVeQCgjPRB
qyjplPc7WRx72nbquw8LIYA=
=oF9p
-----END PGP SIGNATURE-----

Re: Error message - vs-13070

[Oleg Drokin]

Hello!

On Sun, Feb 16, 2003 at 07:33:59AM -0800, Todd Lyons wrote:
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6599945, 
> >sector=4286584
> >end_request: I/O error, dev 03:03 (hda), sector 4286584
> >These errors look to me like a hardware problem (bad sector on the drive).
> >Definately not a reiserfs problem, thanks for the reply Oleg.
> Depends, is 4286584 beyond the end of what really exists, or is that in
> the middle of your valid sectors?

Reads/writes beyond end of device emit different messages.

Bye,
    Oleg

Re: Error message - vs-13070

[Hans Reiser]

Oleg Drokin wrote:

>Hello!
>
>On Sun, Feb 16, 2003 at 07:33:59AM -0800, Todd Lyons wrote:
>  
>
>>>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>>>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6599945, 
>>>sector=4286584
>>>end_request: I/O error, dev 03:03 (hda), sector 4286584
>>>These errors look to me like a hardware problem (bad sector on the drive).
>>>Definately not a reiserfs problem, thanks for the reply Oleg.
>>>      
>>>
>>Depends, is 4286584 beyond the end of what really exists, or is that in
>>the middle of your valid sectors?
>>    
>>
>
>Reads/writes beyond end of device emit different messages.
>
>Bye,
>    Oleg
>
>
>  
>
how about defining that in our faq.

-- 
Hans

Re: Error message - vs-13070

[Oleg Drokin]

Hello!

On Mon, Feb 17, 2003 at 04:36:09PM +0300, Hans Reiser wrote:
> >>>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >>>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=6599945, 
> >>>sector=4286584
> >>>end_request: I/O error, dev 03:03 (hda), sector 4286584
> >>>These errors look to me like a hardware problem (bad sector on the 
> >>>drive).
> >>>Definately not a reiserfs problem, thanks for the reply Oleg.
> >>Depends, is 4286584 beyond the end of what really exists, or is that in
> >>the middle of your valid sectors?
> >Reads/writes beyond end of device emit different messages.
> how about defining that in our faq.

Defining of what?
Q: What does "attempt to access beyond end of device" messages mean?
A: This means that there was attempt to read outside of device.

I see no point in such entries at all.

Bye,
    Oleg

Re: Error message - vs-13070

[Ookhoi]

Andrew Heberle wrote (ao):
> Twice in the last four days I have found the following message in one
> of my systems logs:
> 
> vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find
> stat data of [1718696 1718710 0x0 SD]

[cut]

> I suppose I am just wanting confirmation that based on the error
> message this is likely to be a hardware issure rather than being
> caused by an as-yet unknown corruption bug in reiserfs (I find this
> very unlikely based on my past, very stable history with reiserfs).

Do a dd if=/dev/<rootpartition> of=/dev/null

That either gives you an error (hardware issue) or not. 

Also look at dmesg before and after the dd, and look for new messages.