В Thu, 04 Dec 2014 18:24:11 +0100 Harald Hoyer <[email protected]> пишет:
> On 04.12.2014 18:19, Andrei Borzenkov wrote: > > В Thu, 04 Dec 2014 15:14:00 +0100 > > Harald Hoyer <[email protected]> пишет: > > > >> On 04.12.2014 15:10, Zbigniew Jędrzejewski-Szmek wrote: > >>> On Thu, Dec 04, 2014 at 12:57:36PM +0100, [email protected] wrote: > >>>> From: Harald Hoyer <[email protected]> > >>>> > >>>> If ID_FS_TYPE of a parent is already set, > >>>> then it's something like "linux_raid_member" or "mpath_member" > >>>> and the disk is already in use, so don't handle the partitions > >>> Is this trying to fix an existing problem? > >> > >> yes, for "mpath_member" disk partitions, we should never ever advertise the > >> /dev/disk/by* symlinks or set SYSTEMD_READY for it. > > > > How is it going to work? I mean, first we get device, then it is > > processed by multipathd. At the time rules are processed by udev, we > > have no idea whether it will be added to mpath later. > > For the disk, we should/must the flag set immediately in 62-multipath.rules. > OK it is 56-multipath.rules here and it is actually sets ID_FS_TYPE to "none", but the effect should be the same. I do not see this rule in multipath-tools ... should not it be unified across distros? > The partitions are processed later and IMPORT ID_FS_TYPE from the parent, just > one line above my suggested rule. > _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
