From: Sven Heinicke <sven@research.nj.nec.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: "Simen Thoresen" <simen-tt@online.no>, linux-kernel@vger.kernel.org
Subject: Re: ReiserFS and RAID5
Date: Thu, 24 Jan 2002 16:48:36 -0500 (EST) [thread overview]
Message-ID: <15440.33076.451427.886741@abasin.nj.nec.com> (raw)
In-Reply-To: <20020124215108.71602cb2.skraw@ithnet.com>
In-Reply-To: <15440.22127.875361.718680@abasin.nj.nec.com> <20020124200645.53dca41c.skraw@ithnet.com> <15440.23830.178152.579775@abasin.nj.nec.com> <20020124204938.39fa1960.skraw@ithnet.com> <200201242129150390.0006952E@mail.online.no> <20020124215108.71602cb2.skraw@ithnet.com>
Stephan von Krawczynski writes:
> On Thu, 24 Jan 2002 21:29:15 +0100
> "Simen Thoresen" <simen-tt@online.no> wrote:
>
> > >Is anybody out there that ever survived a hd crash in SW RAID5 config?
> > >(Meaning _without_ need to reboot)
> >
> > Survived and survived....
> >
> > I had a drive lose power (flaky connector) in a 4 drive setup (2x hpt370 dual channel controllers, each with a 30G IBM ide-drive on each channel - Using IDE and Raid-patches for 2.2.17). The result was a readable, but unwritable array. A streamed mp3 played flawlessly while the drive 'died', while my download (over smb) just froze.
> >
> > Rebuilding the array (after a reboot) went ok, but during rebuild the 'new' drive appeared to be drive #5 in the 4-disk set, with drive #3 still dead.
>
> Why is it not writeable? What about a runtime fallover to a spare disk?
>
runtime fallover to the spare disk did not work for me until the
reboot. And even then after the reboot my data was recoverable, but
as describe by my first post, didn't last for long.
Sven
prev parent reply other threads:[~2002-01-24 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 18:46 Sven Heinicke
2002-01-24 19:06 ` Stephan von Krawczynski
2002-01-24 19:49 ` Stephan von Krawczynski
2002-01-24 20:51 ` Stephan von Krawczynski
2002-01-24 19:14 ` Sven Heinicke
2002-01-24 20:29 ` Simen Thoresen
2002-01-24 21:48 ` Sven Heinicke [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=15440.33076.451427.886741@abasin.nj.nec.com \
--to=sven@research.nj.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simen-tt@online.no \
--cc=skraw@ithnet.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
all inboxes | Powered by JetHome®