From: "Anthony R." <russo.lutions@verizon.net>
To: Jeff Mahoney <jeffm@suse.com>
Cc: linux-kernel@vger.kernel.org,
ReiserFS Mailing List <reiserfs-list@namesys.com>
Subject: Re: [PATCH] ReiserFS I/O error Handling [was Re: kernel BUG at fs/reiserfs/prints.c:339! kernel 2.6.5]
Date: Sun, 18 Apr 2004 16:47:57 -0400 [thread overview]
Message-ID: <4082E97D.10605@verizon.net> (raw)
In-Reply-To: <4080573C.4090709@suse.com>
Jeff Mahoney wrote:
> It's most definately a hardware problem. It could be your disk, your
> controller, or the cable connecting them, but somehow hdb1 started
> getting I/O errors. One of them just happened to be in the journal area,
> which ReiserFS doesn't handle well at the moment; it just panics, which
> is what you saw.
FYI, I did an extensive HW test from the vendor and all tests passed.
So I'm not sure it's definitely a HW problem.
I will check out the patches though, thanks.
-- tony
prev parent reply other threads:[~2004-04-18 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 15:12 kernel BUG at fs/reiserfs/prints.c:339! kernel 2.6.5 Anthony R.
2004-04-16 21:59 ` [PATCH] ReiserFS I/O error Handling [was Re: kernel BUG at fs/reiserfs/prints.c:339! kernel 2.6.5] Jeff Mahoney
2004-04-18 20:47 ` Anthony R. [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=4082E97D.10605@verizon.net \
--to=russo.lutions@verizon.net \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox