public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Fao, Sean" <sean.fao@capitalgenomix.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Filesystem/kernel bug?
Date: Wed, 29 Dec 2004 07:54:20 -0500	[thread overview]
Message-ID: <41D2A8FC.7080604@capitalgenomix.com> (raw)
In-Reply-To: <1104251242.3568.30.camel@tribesman.namesys.com>

Vladimir Saveliev wrote:

>Hello
>
>On Tue, 2004-12-28 at 16:52, Fao, Sean wrote:
>  
>
>>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?
>>
>>    
>>
>
>Yes. Please try to reiserfsck your filesystem. Latest reiserfsck can be
>obtained from
>ftp://ftp.namesys.com/pub/reiserfsprogs/reiserfsprogs-3.6.19.tar.gz.
>  
>

Vladimir,

Thank you much for your response.  This is a production email server so 
I had to wait for an appropriate time to shut the system down.

Just a quick summary of what happened.  After rebooting the sever and 
booting from a CD, I ran reiserfsck, which found no corruption in the 
file system.  I then manually checked the directory structure and 
everything looked fine.  I'm not what was wrong, but a reboot apparently 
corrected whatever it was.

I've noticed a couple of patches for reiserfs in the past month or so on 
the LKML.  I'll check after I send this message to see if I can find the 
answer for myself, but, are there any major reiserfs bug fixes related 
to the Linux kernel, which have been corrected since 2.6.9 that I should 
know about?  Also, I'm using a 3ware 8000 series SATA controller, if 
that's at all relevant.

Thanks again for your help,

-- 
Sean

  reply	other threads:[~2004-12-29 12:54 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
2004-12-28 16:27   ` Vladimir Saveliev
2004-12-29 12:54     ` Fao, Sean [this message]
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=41D2A8FC.7080604@capitalgenomix.com \
    --to=sean.fao@capitalgenomix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox