search for: global_filt

...e: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Changes in v2: - dropped patch #5, will be sent separately - move lvmetad statup in own function (patch #2) Thanks, Pino Toscano (4): daemon: lvm-filter: set also global_filter daemon: lvm-filter: start lvmetad better daemon: lvm: improve filter for LVs with activationskip flag set appliance: run systemd-tmpfiles also for /run appliance/init | 3 +-- daemon/daemon.h | 1 + daemon/guestfsd.c | 4 +++- daemon/lvm-filter.c | 50 +++++++++++++++++++++++...

...olumes were listed, only component devices. At the moment, I don't know if the LVs that were activated by the initrd were backed by component devices or the RAID devices, so it's possible that this bug might corrupt software RAID arrays. In order to correct the problem, I had to add a global_filter to /etc/lvm/lvm.conf and rebuild the initrd (dracut -f): global_filter = [ "r|vm_.*_data|", "a|sdd1|", "r|sd..|" ] This filter excludes the LVs that contain VM data, accepts "/dev/sdd1" which is the dm-cache device, and rejects all other partitions on...

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Thanks, Pino Toscano (5): daemon: lvm-filter: set also global_filter daemon: lvm-filter: start lvmetad better daemon: lvm: improve filter for LVs with activationskip flag set daemon: lvm: list PVs/VGs/LVs with --foreign appliance: run systemd-tmpfiles also for /run appliance/init | 3 +-- daemon/lvm-filter.c | 43 +++++++++++++++++++++++++++++++++++...

Simplify how we handle lvm.conf.

...nly component devices. At the moment, I don't know if the > LVs that were activated by the initrd were backed by component devices > or the RAID devices, so it's possible that this bug might corrupt > software RAID arrays. > > In order to correct the problem, I had to add a global_filter to > /etc/lvm/lvm.conf and rebuild the initrd (dracut -f): > global_filter = [ "r|vm_.*_data|", "a|sdd1|", "r|sd..|" ] > > This filter excludes the LVs that contain VM data, accepts "/dev/sdd1" > which is the dm-cache device, and rejects al...

...only component devices. At the moment, I don't know if the > LVs that were activated by the initrd were backed by component devices > or the RAID devices, so it's possible that this bug might corrupt > software RAID arrays. > > In order to correct the problem, I had to add a global_filter to > /etc/lvm/lvm.conf and rebuild the initrd (dracut -f): > global_filter = [ "r|vm_.*_data|", "a|sdd1|", "r|sd..|" ] > > This filter excludes the LVs that contain VM data, accepts "/dev/sdd1" > which is the dm-cache device, and rejects all...

...At the moment, I don't know if the > > LVs that were activated by the initrd were backed by component devices > > or the RAID devices, so it's possible that this bug might corrupt > > software RAID arrays. > > > > In order to correct the problem, I had to add a global_filter to > > /etc/lvm/lvm.conf and rebuild the initrd (dracut -f): > > global_filter = [ "r|vm_.*_data|", "a|sdd1|", "r|sd..|" ] > > > > This filter excludes the LVs that contain VM data, accepts "/dev/sdd1" > > which is the dm...