From: Wilhelm Meier <wilhelm.meier@fh-kl.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm and automatic re-add / incremental mode with usb-disk
Date: Sun, 30 Nov 2008 14:03:29 +0100 [thread overview]
Message-ID: <200811301403.29920.wilhelm.meier@fh-kl.de> (raw)
In-Reply-To: <alpine.DEB.1.10.0811300646440.29266@p34.internal.lan>
Am Sonntag 30 November 2008 schrieb Justin Piszcz:
> On Sun, 30 Nov 2008, Wilhelm Meier wrote:
> > Hi,
> >
> > I'm using debian etch with mdadm 2.5.6-9.
> >
> > I have a md-device /dev/md1000 with two usb-disks as raid1. The
> > array is assembled well if the system boots, if I unplug one of
> > the disks, the array goes to degraded. Thats all ok.
> >
> > If I re-plug the usb-disk, udev discovers the device fine, but
> > mdadm doesn't start the re-add to the md-array. I have to do this
> > but hand.
> >
> > Is there something missing to make this work automatically?
> >
> > I tried the mdm-2.6.2 from etch-backports too. Same effect.
> >
> > Here, if I try to use the --incremental mode, it constructs a new
> > (!) array /dev/md/d_1000 instead of adding it to /dev/md1000.
> > Thats strange to me.
> >
> > I thought I got it working some weeks ago (maybe with earlier /
> > other versions of mdadm or somme missing other tool), but I can't
> > get the puzzle right now.
> >
> > Any hints?
> > --
> > Wilhelm
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-raid" in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
>
> Wilhelm,
>
> As far as I know mdadm never will re-add a
> broken/failed/disconnected disk back into the array. Perhaps what
> you saw before is on an un-clean shutdown or something similar,
> upon reboot the array is checking/re-initializing.
That might be, but what is the difference between doing the re-add and
re-sync on boot (that's what happens!) or if the drive comes back on
a running system.
mdadm can surely determine the state/uuid and do this - the same as on
reboot.
> When you have a failed drive and you re-attach it, it will stay as
> a removed unit and you need to remove it and add it manually as you
> stated.
the only thing I have to do is e.g.
mdadm --re-add /dev/md1000 /dev/sdg1
then it starts reconstructing the right way.
So, my thought was to do this as part of a udev-rule.
But I think this is a common case and therefore there should be a
well-known solution
> Were you seeing something other than this before?
I might be wrong, but I thought it was on debian ...
> Justin.
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-raid" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Wilhelm
next prev parent reply other threads:[~2008-11-30 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 11:31 mdadm and automatic re-add / incremental mode with usb-disk Wilhelm Meier
2008-11-30 11:48 ` Justin Piszcz
2008-11-30 13:03 ` Wilhelm Meier [this message]
2008-11-30 13:10 ` Justin Piszcz
2008-11-30 13:52 ` Wilhelm Meier
2008-12-01 15:21 ` Mario 'BitKoenig' Holbe
2008-12-01 0:32 ` NeilBrown
2008-12-01 6:46 ` Wilhelm Meier
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=200811301403.29920.wilhelm.meier@fh-kl.de \
--to=wilhelm.meier@fh-kl.de \
--cc=jpiszcz@lucidpixels.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.