From: "Diego M. Vadell" <dvadell@lantech.com.ar>
To: linux-raid@vger.kernel.org
Subject: Re: sata_nv and RAID1
Date: Mon, 13 Jun 2005 00:15:42 -0300 [thread overview]
Message-ID: <200506130015.42981.dvadell@lantech.com.ar> (raw)
In-Reply-To: <42AB49BC.50104@tls.msk.ru>
On Saturday 11 June 2005 17:29, Michael Tokarev wrote:
> Jeff Garzik wrote:
> > On Sat, Jun 11, 2005 at 04:13:42PM +0000, Diego M. Vadell wrote:
> >>Hi,
> >> A new computer arrived at work with 4 160GB SATA disks. I made a
> >>couple of RAID 1 (mirror) with two disks each, and then joined them wih
> >>LVM. Now I have 320GB in my root volume.
> >>
> >>My boss asked me to test it, so we all gathered and unplugged the data
> >>cable of one of the disks. I was hoping to see linux making warnings for
> >
> > Hotplug is not supported yet. Don't do that :)
>
> It isn't hotPLUG -- it's hotUNplug. Happens when drive is dying for
> example, or when the cable is flaky, or due to millions of other
> reasons... And.. I for one expect linux to react to such a situation
> *somehow* - after all, raid is used for this very stuff too, to be
> able to continue running a system if one of the drives failed...
>
> /mjt
So I thought... Who's fault is it? Is it something missing from sata_nv or
from md? How hard could it be to implement (I dont know a thing, but maybe
its just a matter of returning an error somewhere, as I dont want to retry or
nothing but informing the md layer that it has to forget about that disk)?
Has anybody started to do this?
Thanks a lot,
-- Diego.
next prev parent reply other threads:[~2005-06-13 3:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 16:13 sata_nv and RAID1 Diego M. Vadell
2005-06-11 19:26 ` Jeff Garzik
2005-06-11 20:29 ` Michael Tokarev
2005-06-13 3:15 ` Diego M. Vadell [this message]
2005-06-13 6:45 ` Jeff Garzik
2005-06-13 11:57 ` Michael Tokarev
2005-06-13 12:27 ` Peter T. Breuer
2005-06-13 14:40 ` Diego M. Vadell
2005-06-13 16:07 ` Peter T. Breuer
2005-06-13 16:51 ` Diego M. Vadell
2005-06-13 17:59 ` Jeff Garzik
2005-06-13 21:00 ` Diego M. Vadell
2005-06-13 21:20 ` Jeff Garzik
2005-06-13 21:41 ` Diego M. Vadell
[not found] ` <1118818568.3089.5.camel@raz-laptop>
[not found] ` <200506151427.09114.dvadell@lantech.com.ar>
2005-06-16 6:43 ` raz ben jehuda
2005-06-14 21:11 ` Molle Bestefich
2005-06-13 19:00 ` Peter T. Breuer
2005-06-13 20:41 ` Raz Ben-Jehuda(caro)
2005-06-13 21:16 ` Diego M. Vadell
2005-06-14 21:11 ` Molle Bestefich
2005-06-14 21:37 ` Michael Tokarev
2005-06-14 22:10 ` Diego M. Vadell
2005-06-14 22:17 ` Michael Tokarev
2005-06-15 0:08 ` Jeff Garzik
2005-06-14 22:26 ` Molle Bestefich
2005-06-14 23:07 ` Bill Davidsen
2005-06-14 23:18 ` Molle Bestefich
2005-06-15 0:12 ` Jeff Garzik
2005-06-15 0:19 ` Molle Bestefich
2005-06-14 23:46 ` Mike Hardy
2005-06-15 0:11 ` Jeff Garzik
2005-06-15 0:34 ` Guy
2005-06-14 21:53 ` David Greaves
2005-06-14 22:30 ` Molle Bestefich
2005-06-15 19:17 ` Mark Hahn
2005-06-15 19:32 ` Molle Bestefich
2005-06-15 19:34 ` Molle Bestefich
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=200506130015.42981.dvadell@lantech.com.ar \
--to=dvadell@lantech.com.ar \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).