From: Oleg Drokin <green@namesys.com>
To: berthiaume_wayne@emc.com
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs oops
Date: Thu, 10 Apr 2003 22:09:29 +0400 [thread overview]
Message-ID: <20030410220929.A11132@namesys.com> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D007AA83FC@CORPUSMX1>
Hello!
On Thu, Apr 10, 2003 at 01:56:05PM -0400, berthiaume_wayne@emc.com wrote:
> Oleg, I'm seeing the attached oops's when a hard drive failure is
> encountered. There are four drives in RAID 1. Is it normal for reiserfs to
> oops when a drive fails?
Hm, You mean that all four drives have a bad block in the same place?
I thought that the whole idea of RAID1 is that when
one hard drive fails, other will deliver necessary data.
reiserfs does not handle io errors (especially in journal area) very gracefully
and should just panic (not dereference something bad like in your case which
is something very suspicious). Jeff Mahoney of SuSE is working on having more
redundancy in such cases.
> Attached oops file...
Hm, this one is certainly looking very strange.
I will comment more on it tomorrow. Do you have any extra reiserfs patches
on top of your 2.4.19 kernel?
Bye,
Oleg
next prev parent reply other threads:[~2003-04-10 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 17:56 Reiserfs oops berthiaume_wayne
2003-04-10 18:06 ` Lars Marowsky-Bree
2003-04-10 18:09 ` Oleg Drokin [this message]
2003-04-10 18:26 ` Anders Widman
-- strict thread matches above, loose matches on Subject: below --
2003-04-10 18:32 Bingner Sam J Contractor PACAF CSS/SCHE
2003-04-23 21:08 berthiaume_wayne
2003-04-24 5:21 ` Oleg Drokin
2003-04-24 12:29 berthiaume_wayne
2004-03-27 1:40 reiserfs oops Wakko Warner
2004-03-27 11:28 ` Oleg Drokin
2005-02-22 12:22 Samuel Liddicott
2005-02-22 14:33 ` Vladimir Saveliev
2005-02-22 15:51 ` Samuel Liddicott
2005-02-22 22:00 ` Sam Liddicott
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=20030410220929.A11132@namesys.com \
--to=green@namesys.com \
--cc=berthiaume_wayne@emc.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.