From: "Fao, Sean" <sean.fao@capitalgenomix.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Filesystem/kernel bug?
Date: Tue, 28 Dec 2004 08:52:00 -0500 [thread overview]
Message-ID: <41D16500.9070903@capitalgenomix.com> (raw)
In-Reply-To: <41D02F54.8070107@capitalgenomix.com>
Update:
I found these events --and many similar-- in my log file.
Dec 26 17:55:43 cgx-mail ReiserFS: warning: is_tree_node: node level 0
does not match to the expected one 1
Dec 26 17:55:43 cgx-mail ReiserFS: sda3: warning: vs-5150:
search_by_key: invalid format found in block 13706028. Fsck?
Dec 26 17:55:43 cgx-mail ReiserFS: sda3: warning: vs-13070:
reiserfs_read_locked_inode: i/o failure occurred trying to find stat
data of [30749 74887 0x0 SD]
Dec 26 17:55:43 cgx-mail ReiserFS: warning: is_tree_node: node level 0
does not match to the expected one 1
Dec 26 17:55:43 cgx-mail ReiserFS: sda3: warning: vs-5150:
search_by_key: invalid format found in block 13706028. Fsck?
Dec 26 17:55:43 cgx-mail ReiserFS: sda3: warning: vs-13070:
reiserfs_read_locked_inode: i/o failure occurred trying to find stat
data of [30749 74888 0x0 SD]
Dec 26 17:55:43 cgx-mail ReiserFS: warning: is_tree_node: node level 0
does not match to the expected one 1
Dec 26 17:55:43 cgx-mail ReiserFS: sda3: warning: vs-5150:
search_by_key: invalid format found in block 13706028. Fsck?
Dec 26 17:55:43 cgx-mail ReiserFS: sda3: warning: vs-13070:
reiserfs_read_locked_inode: i/o failure occurred trying to find stat
data of [30749 74888 0x0 SD]
Does this shed any new light? Does it look like I might have a
corrupted file system?
Thanks again,
--
Sean
next prev parent reply other threads:[~2004-12-28 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 15:50 Filesystem/kernel bug? Fao, Sean
2004-12-28 13:52 ` Fao, Sean [this message]
2004-12-28 16:27 ` Vladimir Saveliev
2004-12-29 12:54 ` Fao, Sean
2004-12-29 13:55 ` Jakob Oestergaard
2004-12-29 14:38 ` Fao, Sean
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=41D16500.9070903@capitalgenomix.com \
--to=sean.fao@capitalgenomix.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 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.