From: Oleg Drokin <green@namesys.com>
To: joe briggs <jbriggs@briggsmedia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How can you trace a reiserfs error to the device or filesystem?
Date: Mon, 16 Jun 2003 11:50:51 +0400 [thread overview]
Message-ID: <20030616075051.GA12646@namesys.com> (raw)
In-Reply-To: <200306151724.49277.jbriggs@briggsmedia.com>
Hello!
On Sun, Jun 15, 2003 at 05:24:49PM -0400, joe briggs wrote:
> I get reiserfs errors like the ones below from my /var/log/syslog. Is there a
> way to tell what device they are coming from?
Unfortunatelly, no.
But we have patches that we hope to merge in mainline eventually.
> csi kernel: is_tree_node: node level 35718 does not match expected one 1
> csi kernel: vs-5150: search_by_key: invalid format found in block 9406, Fsck?
> csi kernel: vs-13050: reiserfs_update_sd: i/o failure occurred trying to
> update [10145 51612 0x0 SD] stat datais_tree_node: node level 35718 does not
> match the expected one 1
Bye,
Oleg
prev parent reply other threads:[~2003-06-16 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 21:24 How can you trace a reiserfs error to the device or filesystem? joe briggs
2003-06-16 7:50 ` Oleg Drokin [this message]
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=20030616075051.GA12646@namesys.com \
--to=green@namesys.com \
--cc=jbriggs@briggsmedia.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox