From: Lee Revell <rlrevell@joe-job.com>
To: Chase Venters <chase.venters@clientec.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (was: Oops in do_page_fault) ReiserFS problems... (Now with full trace)
Date: Tue, 25 Oct 2005 23:11:15 -0400 [thread overview]
Message-ID: <1130296276.4483.61.camel@mindpipe> (raw)
In-Reply-To: <200510252136.14096.chase.venters@clientec.com>
On Tue, 2005-10-25 at 21:35 -0500, Chase Venters wrote:
> #1 - I've never seen any of the disks in this raid10 (md1 mounted
> on /) produce any CRC errors (though correct me if I'm wrong, I don't
> see any reason the kernel should BUG()/oops/panic because of corrupted
> filesystems)
Reiser3 is notoriously bad at handling error conditions like this. I
personally stopped using reiser3 when I had a power loss that caused
chunks of files to end up in other files. I was able to fix the
critical ones with a text editor but who knows what other damage it did.
Lee
next prev parent reply other threads:[~2005-10-26 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 19:00 Oops in do_page_fault chase.venters
2005-10-25 19:59 ` Lee Revell
2005-10-26 2:35 ` (was: Oops in do_page_fault) ReiserFS problems... (Now with full trace) Chase Venters
2005-10-26 3:11 ` Lee Revell [this message]
2005-10-25 20:20 ` Oops in do_page_fault John Stoffel
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=1130296276.4483.61.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=chase.venters@clientec.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