From: Paul Rolland <rol@as2917.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: rol@as2917.net
Subject: SATA hotplug device renaming and dmraid...
Date: Tue, 20 May 2008 20:11:57 +0200 [thread overview]
Message-ID: <20080520201157.21c31481@tux.DEF.witbe.net> (raw)
Hello,
I'm using a machine that supports SATA hotplug and with and Intel ESB2
(Fake)Raid controller.
I've configured a raid1 (mirror) array using dmraid, that is made of
/dev/sda and /dev/sdb, and seen by the OS as /dev/mapper/isw_xxxxxxx_RAID1
My problem is that when I unplug and replug a disk, it is assigned a
new name (/dev/sdc first time as this is the first name available), and
so it is no more considered as being part of the RAID array.
Is this an expected behavior ? Is there a way (using dmraid/dmsetup) to
instruct kernel of the changes ?
It seems that udev can get events from device-mapper, from
Documentations/device-mapper/dm-xxxx.txt, but I don't really see how to use
this to notify of a disk change in the array...
Regards,
Paul
reply other threads:[~2008-05-20 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080520201157.21c31481@tux.DEF.witbe.net \
--to=rol@as2917.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®