From: Ric Wheeler <ric@emc.com>
To: Leon Woestenberg <leon.woestenberg@gmail.com>
Cc: linux-raid@vger.kernel.org, Tejun Heo <htejun@gmail.com>,
Greg KH <gregkh@suse.de>
Subject: Re: libata hotplug and md raid?
Date: Wed, 13 Sep 2006 06:51:21 -0400 [thread overview]
Message-ID: <4507E2A9.7070306@emc.com> (raw)
In-Reply-To: <c384c5ea0609130311t4005e5aam153251fc6bbbdfb8@mail.gmail.com>
(Adding Tejun & Greg KH to this thread)
Leon Woestenberg wrote:
> Hello all,
>
> I am testing the (work-in-progress / upcoming) libata SATA hotplug.
> Hotplugging alone seems to work, but not well in combination with md
> RAID.
>
> Here is my report and a question about intended behaviour. Mainstream
> 2.6.17.11 kernel patched with libata-tj-2.6.17.4-20060710.tar.bz2 from
> http://home-tj.org/files/libata-tj-stable/.
>
> Supermicro P8SCT motherboard with Intel ICH6R, using AHCI libata driver.
>
> In short, I use ext3 over /dev/md0 over 4 SATA drives /dev/sd[a-d]
> each driven by libata ahci. I unplug then replug the drive that is
> rebuilding in RAID-5.
>
> When I unplug a drive, /dev/sda is removed, hotplug seems to work to
> the point where proc/mdstat shows the drive failed, but not removed.
>
> Every other notion of the drive (in kernel and udev /dev namespace)
> seems to be gone after unplugging. I cannot manually removed the drive
> using mdadm, because it tells me the drive does not exist.
>
> Replugging the drive brings it back as /dev/sde, md0 will not pick it up.
I have a similar setup, AHCI + 4 drives but using a RAID-1 group. The
thing that you are looking for is "persistent device naming" and should
work properly if you can tweak udev/hotplug correctly.
I have verified that a drive pull/drive reinsert on a mainline kernel
with a SLES10 base does provide this (first insertion gives me sdb, pull
followed by reinsert still is sdb), but have not tested interaction with
RAID since I am focused on the bad block handling at the moment. I will
add this to my list ;-)
>
> The expected behaviour (from me) is that the drive re-appears as
> /dev/sda.
>
> What is the intended behaviour of md in this case?
>
> Should some user-space application fail-remove a drive as a pre-action
> of the unplug event from udev, or should md fully remove the drive
> within kernel space??
>
> See kernel/udev/userspace messages in chronological order,
> with my actions marked between >>> <<<, at this web
> page:
>
> http://pastebin.ca/168798
>
> Thanks,
> --
> Leon
>
>
next prev parent reply other threads:[~2006-09-13 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 10:11 libata hotplug and md raid? Leon Woestenberg
2006-09-13 10:51 ` Ric Wheeler [this message]
2006-09-13 11:06 ` Tejun Heo
2006-09-13 11:45 ` Leon Woestenberg
2006-09-14 11:44 ` Turbo Fredriksson
2006-09-14 12:24 ` Leon Woestenberg
2006-09-14 23:23 ` Greg KH
2006-09-15 19:38 ` Leon Woestenberg
2006-10-17 0:23 ` Mark Lord
2006-10-17 1:58 ` Neil Brown
2006-10-17 8:07 ` Gabor Gombas
2006-10-17 8:11 ` Gabor Gombas
2007-01-10 22:55 ` Mike Accetta
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=4507E2A9.7070306@emc.com \
--to=ric@emc.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=leon.woestenberg@gmail.com \
--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 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.