From: Xiao Ni <xni@redhat.com>
To: linux-raid@vger.kernel.org
Cc: neilb@suse.com, jes.sorensen@gmail.com
Subject: [MDADM PATCH 0/2] /dev/md0 can't be released immediatly
Date: Tue, 19 Sep 2017 14:06:45 +0800 [thread overview]
Message-ID: <1505801207-10096-1-git-send-email-xni@redhat.com> (raw)
Hi all
The device node /dev/md0 can't be released immediatly after the command
mdadm -S /dev/md0 or mdadm -Ss.
We should give enough time to udev to handle udev events.
Xiao Ni (2):
Close mdfd before returning main function
Give enough time to udev to handle events
Create.c | 2 +-
mdadm.c | 16 ++++++++++++++++
2 files changed, 17 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2017-09-19 6:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 6:06 Xiao Ni [this message]
2017-09-19 6:06 ` [MDADM PATCH 1/2] Close mdfd before returning main function Xiao Ni
2017-10-02 17:27 ` Jes Sorensen
2017-09-19 6:06 ` [MDADM PATCH 2/2] Give enough time to udev to handle events Xiao Ni
2017-09-19 6:49 ` NeilBrown
2017-09-30 8:14 ` Xiao Ni
2017-10-02 17:28 ` Jes Sorensen
2017-10-02 23:00 ` NeilBrown
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=1505801207-10096-1-git-send-email-xni@redhat.com \
--to=xni@redhat.com \
--cc=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
/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).