On Wed, 2022-03-09 at 11:26 -0600, David Teigland wrote:
> >
> > If we started pvscan later, in RUN, and a VG became complete,
> > instead
> > of printing the VG name to stdout, it could run the "systemd-run"
> > command for lvm-activate-${VG}, which is currently called in 69-dm-
> > lvm.rules, directly instead, by fork()ing and exec()ing
> > "systemd-run".
> > That was what I meant. Just a thought, not sure if it really works.
>
> Having pvscan fork systemd-run vgchange -aay doesn't sound nice at
> all.
> The point of this new design is clean up and simplify things,
> separating
> the scanning from the activation: pvscan just scans the device, and
> vgchange activates the VG.
It was just a thought, trying to figure out a way to move this logic in
to RUN completely, so that pvscan would be able to access udev
properties.
I'll wait for the fix for the external_device_info_source=udev case,
which you mentioned in your previous post.
Thanks,
Martin
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
