Description of problem: Prepare two different size disks, which one has a LV on the VG, two VGs have the same name but different uuid. Add two disk then run "lvm-clear-filter", it failed by “device-mapper: create ioctl on vg-lv failed: Device or resource busy” Version-Release number of selected component (if applicable): libguestfs-1.22.6-22.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. # dd if=/dev/zero of=test1.img bs=1M count=500 # guestfish -a test1.img run : vgcreate vg /dev/sda : lvcreate lv vg 100 2. # dd if=/dev/zero of=test2.img bs=1M count=500 # guestfish -a test2.img run : vgcreate vg /dev/sda : lvcreate lv vg 100 3. # guestfish -a test1.img -a test2.img run : lvm-clear-filter Actual results: Expected results: Additional info:
On Fedora Rawhide, I see this set of errors. The final error is the one reported. $ guestfish -N test1=lv exit $ guestfish -N test2=lv exit $ guestfish -a test1 -a test2 run : lvm-clear-filter libguestfs: error: lvm_clear_filter: vgchange: /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Duplicate VG name VG: Existing ozXPwo-GxJZ-ohnB-OUEQ-1rSO-Yce8-uccH5w (created here) takes precedence over 3wodJT-5GO4-XI4q-NxTo-TE3e-YiKo-gashdX /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Duplicate VG name VG: Existing ozXPwo-GxJZ-ohnB-OUEQ-1rSO-Yce8-uccH5w (created here) takes precedence over 3wodJT-5GO4-XI4q-NxTo-TE3e-YiKo-gashdX /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Duplicate VG name VG: Existing 3wodJT-5GO4-XI4q-NxTo-TE3e-YiKo-gashdX (created here) takes precedence over ozXPwo-GxJZ-ohnB-OUEQ-1rSO-Yce8-uccH5w /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Duplicate VG name VG: Existing ozXPwo-GxJZ-ohnB-OUEQ-1rSO-Yce8-uccH5w (created here) takes precedence over 3wodJT-5GO4-XI4q-NxTo-TE3e-YiKo-gashdX /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory device-mapper: create ioctl on VG-LV failed: Device or resource busy
This is a real bug, but one which only affects peculiar test cases (not any likely customer scenario). It's better to reassign this bug to upstream to track it, but it's not something we especially care about in RHEL.