From: Bernd Schubert <bs@q-leap.de>
To: linux-raid@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net,
416512@bugs.debian.org, Neil Brown <neilb@suse.de>
Subject: Re: removed disk && md-device
Date: Wed, 09 May 2007 13:39:53 +0000 [thread overview]
Message-ID: <200705091539.53863.bs@q-leap.de> (raw)
In-Reply-To: <20070509131450.GA31985@lapse.madduck.net>
On Wednesday 09 May 2007 15:14:50 martin f krafft wrote:
> also sprach Bernd Schubert <bs@q-leap.de> [2007.05.09.1417 +0200]:
> > Problem-1) When the disk fails, udev will remove it from /dev.
> > Unfortunately this will make it impossible to remove the disk or its
> > partitions from /dev/mdX device, since mdadm tries to read the device
> > fail and will abort if this file is not there.
>
> Please also see http://bugs.debian.org/416512. It would be nice if
> you could keep 416512@bugs.debian.org on CC.
>
> mdadm upstream knows of the problem. See the bug log.
Ah, so Goswin already wrote a bug report :) Actually Goswin first did run into
this problem here while doing some internal tests, but today we have it on a
customer system.
Neil Brown <neilb@suse.de> [2007.04.02.0953 +0200]:
>Hmmm... this is somewhat awkward. You could argue that udev should be
>taught to remove the device from the array before removing the device
>from /dev. But I'm not convinced that you always want to 'fail' the
>device. It is possible in this case that the array is quiescent and
>you might like to shut it down without registering a device failure...
Hmm, the the kernel advised hotplug to remove the device from /dev, but you
don't want to remove it from md? Do you have an example for that case?
>It is still possible to fail and remove the device by
>writing "faulty" and then "remove" to
> /sys/block/mdX/md/dev-YYY/state
>Maybe an mdadm command that will do that for a given device, or for
>all components of a given array if the 'dev' link is 'broken', or even
>for all devices for all array.
> mdadm --fail-unplugged --scan
>or
> mdadm --fail-unplugged /dev/md3
Ok, so one could run this as cron script. Neil, may I ask if you already
started to work on this? Since we have the problem on a customer system, we
should fix it ASAP, but at least within the next 2 or 3 weeks. If you didn't
start work on it yet, I will do...
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-05-09 13:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 12:17 removed disk && md-device Bernd Schubert
2007-05-09 13:14 ` martin f krafft
2007-05-09 13:39 ` Bernd Schubert [this message]
2007-05-10 7:12 ` Neil Brown
2007-05-10 14:33 ` David Greaves
2007-05-11 1:36 ` Neil Brown
2007-05-11 8:51 ` Michael Tokarev
2007-05-11 9:22 ` Bernd Schubert
2007-05-11 20:39 ` Bill Davidsen
2007-05-15 9:52 ` Goswin von Brederlow
2007-05-11 8:52 ` David Greaves
2007-05-11 15:05 ` David Greaves
2007-05-11 20:50 ` David Greaves
2007-05-10 18:17 ` Bernd Schubert
2007-05-11 6:16 ` Neil Brown
2007-05-11 20:47 ` Bill Davidsen
2007-05-16 21:19 ` Colin McCabe
2007-05-09 21:41 ` Michael Tokarev
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=200705091539.53863.bs@q-leap.de \
--to=bs@q-leap.de \
--cc=416512@bugs.debian.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).