From: Oleg Drokin <green@linuxhacker.ru>
To: James Bromberger <james@rcpt.to>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 && md raid1 && reiserfs panic
Date: Mon, 9 Feb 2004 03:56:59 +0200 [thread overview]
Message-ID: <20040209015659.GC1978@linuxhacker.ru> (raw)
In-Reply-To: <20040209011040.GB27378@phobe.internal.pelicanmanufacturing.com.au>
Hello!
On Mon, Feb 09, 2004 at 09:10:40AM +0800, James Bromberger wrote:
> > JB> The symptoms: rm a file from a working RAID1 md reiserfs filesystem,
> > JB> and I get a panic, rm(1) segfaults, and all further I/O to any interactive
> > JB> shells stop. The entire system is rednered incapable; reboot (via
> > JB> ctrl-alt-del) doesnt shutdown and the only action is to hard reset the box.
> >
> > What if you run reiserfsck over the volume that seems to be corrupted,
> > then fix the errors and then retry the operation?
> Yes! That was it. Attached is the output I captured from reiserfsck.
> It identified the very file I was attempting to remove that was causing
> the segfault in rm(1).
> So I guess this is a reiserfs specific issue when it kills all disk I/O
> when this correcption happens. Hmm.
Yes, in-kernel reiserfs is not all that good when it comes to corrupted
filesystems yet. The source of this corruption is yet unknown, though.
You can fix the corruption with reiserfsck --fix-fixable, or
reiserfsck --rebuild-tree if first one does not work.
Be sure to use latest reiserfsprogs.
Bye,
Oleg
prev parent reply other threads:[~2004-02-09 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 11:23 2.4.23 && md raid1 && reiserfs panic James Bromberger
2004-02-08 17:22 ` Oleg Drokin
2004-02-09 1:10 ` James Bromberger
2004-02-09 1:56 ` 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=20040209015659.GC1978@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=james@rcpt.to \
--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