linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Parschauer <sebastian.riemer@profitbricks.com>
To: linux-hotplug@vger.kernel.org
Cc: Linux RAID <linux-raid@vger.kernel.org>,
	artur.paszkiewicz@intel.com,
	Francis Moreau <francis.moro@gmail.com>
Subject: udev 215 creates inactive MD devices upon stopping them
Date: Thu, 24 Jul 2014 14:48:42 +0000	[thread overview]
Message-ID: <53D11CCA.1050602@profitbricks.com> (raw)

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>bdb81ef088afd3b4c72b516beb5610f8c93a0d
> 
> 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é18a1b5a94f270186dca59156354acd2a596494
> 

Thanks,
Sebastian

                 reply	other threads:[~2014-07-24 14:48 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=53D11CCA.1050602@profitbricks.com \
    --to=sebastian.riemer@profitbricks.com \
    --cc=artur.paszkiewicz@intel.com \
    --cc=francis.moro@gmail.com \
    --cc=linux-hotplug@vger.kernel.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).