From: Sebastian Parschauer <sebastian.riemer@profitbricks.com>
To: systemd-devel@freedesktop.org, Kay Sievers <kay@vrfy.org>
Cc: Linux RAID <linux-raid@vger.kernel.org>,
artur.paszkiewicz@intel.com,
Francis Moreau <francis.moro@gmail.com>
Subject: Re: udev 215 creates inactive MD devices upon stopping them
Date: Thu, 24 Jul 2014 17:48:05 +0200 [thread overview]
Message-ID: <53D12AB5.5090102@profitbricks.com> (raw)
In-Reply-To: <53D11CCA.1050602@profitbricks.com>
[resending to the correct mailing list]
Hi,
as discussed on linux-raid, please fix the bug that udev 215 creates
inactive MD devices upon stopping them.
Reference: http://www.spinics.net/lists/raid/msg46676.html
Reported-by: Francis Moreau <francis.moro@gmail.com>
An open() call to /dev/mdX after creating it with mknod is enough to
create such inactive MD device.
According to Artur the issue is caused by this change in udev:
> commit 3ebdb81ef088afd3b4c72b516beb5610f8c93a0d
> Author: Kay Sievers <kay at vrfy.org>
> Date: Sun Apr 13 19:54:27 2014 -0700
>
> udev: serialize/synchronize block device event handling with file locks
>
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=3ebdb81ef088afd3b4c72b516beb5610f8c93a0d
>
> It seems that they have already disabled this for dm for some reason,
> but not for md:
>
> commit e918a1b5a94f270186dca59156354acd2a596494
> Author: Kay Sievers <kay@vrfy.org>
> Date: Tue Jun 3 16:49:38 2014 +0200
>
> udev: exclude device-mapper from block device ownership event locking
>
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=e918a1b5a94f270186dca59156354acd2a596494
>
Thanks,
Sebastian
next prev parent reply other threads:[~2014-07-24 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 14:48 udev 215 creates inactive MD devices upon stopping them Sebastian Parschauer
2014-07-24 14:48 ` Sebastian Parschauer
2014-07-24 15:48 ` Sebastian Parschauer [this message]
2014-07-24 21:53 ` Kay Sievers
2014-07-24 22:17 ` 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=53D12AB5.5090102@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=artur.paszkiewicz@intel.com \
--cc=francis.moro@gmail.com \
--cc=kay@vrfy.org \
--cc=linux-raid@vger.kernel.org \
--cc=systemd-devel@freedesktop.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 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.