Forwarding to systemd-devel@ for http://bugs.gentoo.org/show_bug.cgi?id=517986
-------- Original Message -------- Subject: Re: udev 215 creates inactive MD devices upon stopping them Date: Thu, 24 Jul 2014 17:48:05 +0200 From: Sebastian Parschauer <sebastian.rie...@profitbricks.com> To: systemd-de...@freedesktop.org, Kay Sievers <k...@vrfy.org> CC: Linux RAID <linux-r...@vger.kernel.org>, artur.paszkiew...@intel.com, Francis Moreau <francis.m...@gmail.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.m...@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 <k...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
