From: Wilhelm Meier <wilhelm.meier@fh-kl.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm and automatic re-add / incremental mode with usb-disk
Date: Mon, 1 Dec 2008 07:46:55 +0100 [thread overview]
Message-ID: <200812010746.55418.wilhelm.meier@fh-kl.de> (raw)
In-Reply-To: <84ecb37ac21f70e48b360192851e2f3a.squirrel@neil.brown.name>
Am Montag 01 Dezember 2008 schrieb NeilBrown:
> On Sun, November 30, 2008 10:31 pm, 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?
>
> You would need to put some magic in udev.
> Something in /etc/udev/rules.d would need to do something like
> RUN+="/sbin/mdadm -I ..the..device.name"
Yes, I tried that and it works half-the-way: as I wrote in another
posting, mdadm -I does not allow the -c configfile option. Because I
use a different config for a special set of devices, mdadm -I does
not know the uuid's of the arrays of this special config file and
therefore creates a new array with a different naming scheme (and
different major/minor dev-numbers) (see below).
>
> if the detected device was one that you want to be added to an
> array. I have tried this yet so I don't know the details of how to
> make it work.
>
> > 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.
>
> --incremental only works properly if the array was created by
> --incremental.
Thats a point I don't understand.
Should I use --increment instead of normal creation and
later --assemble?
Why is this different?
Can this work together, I mean: can I --assemble arrays (as most
distros do that on boot) and later --incremental create/reconstruct
other arrays?
> You might be able to make it work better by
> running
> mdadm -Ir
>
> first. This recreates /var/run/mdadm/map.
--
Wilhelm
prev parent reply other threads:[~2008-12-01 6:46 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
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 [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=200812010746.55418.wilhelm.meier@fh-kl.de \
--to=wilhelm.meier@fh-kl.de \
--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 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.