From: Neil Brown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-raid@vger.kernel.org
Subject: [PULL REQUEST] one more fix for md: destroy partitions when stopping an array.
Date: Fri, 31 Oct 2008 12:05:56 +1100 [thread overview]
Message-ID: <18698.23028.593060.515670@notabene.brown> (raw)
Just one more... :-)
md: destroy partitions and notify udev when md array is stopped.
md arrays are not currently destroyed when they are stopped - they
remain in /sys/block. Last time I tried this I tripped over locking
too much.
A consequence of this is that udev doesn't remove anything from /dev.
This is rather ugly.
As an interim measure until proper device removal can be achieved,
make sure all partitions are removed using the BLKRRPART ioctl, and
send a KOBJ_CHANGE when an md array is stopped.
Signed-off-by: NeilBrown <neilb@suse.de>
Thanks,
NeilBrown
The following changes since commit f8d56f1771e4867acc461146764b4feeb5245669:
Linus Torvalds (1):
Merge branch 'for-linus' of git://neil.brown.name/md
are available in the git repository at:
git://neil.brown.name/md for-linus
NeilBrown (1):
md: destroy partitions and notify udev when md array is stopped.
drivers/md/md.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
reply other threads:[~2008-10-31 1:05 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=18698.23028.593060.515670@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=torvalds@linux-foundation.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