From: Oleg Drokin <green@namesys.com>
To: Andrew Heberle <heberle@westnet.com.au>
Cc: reiserfs-list@namesys.com
Subject: Re: Error message - vs-13070
Date: Fri, 14 Feb 2003 19:39:50 +0300 [thread overview]
Message-ID: <20030214193950.A27507@namesys.com> (raw)
In-Reply-To: <5.2.0.9.0.20030215000534.018ed008@mail.bogus.home>
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
next prev parent reply other threads:[~2003-02-14 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 16:26 Error message - vs-13070 Andrew Heberle
2003-02-14 16:39 ` Oleg Drokin [this message]
2003-02-16 12:39 ` Andrew Heberle
2003-02-16 15:33 ` Todd Lyons
2003-02-17 6:15 ` Oleg Drokin
2003-02-17 13:36 ` Hans Reiser
2003-02-17 13:41 ` Oleg Drokin
2003-02-14 17:40 ` Ookhoi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030214193950.A27507@namesys.com \
--to=green@namesys.com \
--cc=heberle@westnet.com.au \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.