From: Michal Soltys <nozo@ziu.info>
To: linux-raid@vger.kernel.org
Subject: mdadm (on partitionable arrays) and partition uevents
Date: Sat, 11 Aug 2007 14:05:39 +0200 [thread overview]
Message-ID: <46BDA613.1020604@ziu.info> (raw)
During doing some tests, I've found a slight delay of partition related
uevents, when raid devices are assembled/stopped.
For example - consider md/d0 with 1 partition created. The array is unassembled.
1) mdadm -A /dev/md/d0
will generate "change" even properly for md/d0, but "add' uevent for its
partition, will be delayed until some next mdadm operation or some partition
related operation - fdisk, etc.
2) mdadm -S /dev/md/d0
Analogously, "remove" for partitions will be run on some later mdadm
command, or even unsuccessful attempt to fdisk that array.
To not cause any potential conflicts, mdadm.conf had symlinks=no, and mdadm
was used only with directory based names, whereas udev had no custom rules
regarding any md devices (so only standard /dev/md_d[0-9]* and /dev/md[0-9]*
were created).
Tested under udev 114, mdadm 2.6.2 on two different systems (one arch 64bit,
the other 32bit).
I'm not actually sure if it's even a bug in the first place, or if it has
anything to do with mdadm, but reporting it nonetheless.
reply other threads:[~2007-08-11 12: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=46BDA613.1020604@ziu.info \
--to=nozo@ziu.info \
--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 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).