From: Dan Oglesby <doglesby@teleformix.com>
To: reiserfs-list@namesys.com
Subject: ReiserFS errors in /var/log/messages
Date: Wed, 14 Sep 2005 11:56:13 -0500 [thread overview]
Message-ID: <4328562D.4010901@teleformix.com> (raw)
I recently started seeing the following message repeating in my
/var/log/messages file on a server:
kernel: is_leaf: free space seems wrong: level=1, nr_items=39,
free_space=0 rdkey
kernel: vs-5150: search_by_key: invalid format found in block 5405324. Fsck?
kernel: vs-13070: reiserfs_read_inode2: i/o failure occurred trying to
find stat data of [11 618208 0x0 SD]
Every day a large filesystem rsyncs to another filesystem for
backup/redundancy, and it looks like this coincides with the error
listed above. It repeats about 13 times every time rsync runs. It's
always the same block number.
This filesystem lives on a 3Ware RAID-5 array, and is running a 2.4.20
kernel from RedHat that we cannot upgrade due to hardware and software
dependancies.
I'm planning on downloading the latest version of the ReiserFS tools,
and checking for errors/repairing.
Anyone know what this error means, so I have a better idea of what I'm
dealing with? I find it strange that I could have a block error on a
logical drive (the RAID-5 device).
Thanks...
--Dan
reply other threads:[~2005-09-14 16:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4328562D.4010901@teleformix.com \
--to=doglesby@teleformix.com \
--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.