[opensuse] lvm on a drbd device ?
I need a second pair of eyes. Or a third or a fourth. I am working on a drbd test setup. Two machines, each has a 2Tb disk, 3 partitions (root, swap, drbd). drbd will eventually be controlled by pacemaker, for now I am just starting and stopping manually. I had drbd working fine, but then I created an lvm PV on /dev/drbd1 and carved out a 10Gb LV. When I boot up either of the two systems, I see a PV: office36:~ # pvdisplay WARNING: Device for PV k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW not found or rejected by a filter. WARNING: Device for PV k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW not found or rejected by a filter. --- Physical volume --- PV Name unknown device VG Name Grp1 PV Size 1.77 TiB / not usable 3.52 MiB Allocatable yes PE Size 4.00 MiB Total PE 463093 Free PE 460533 Allocated PE 2560 PV UUID k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW At this point drbd is not yet running, so there is no /dev/drbd1. I guess lvm start-up sort of gleans the above from /dev/sda3, the drbd partition. I can't start drbd either - office36:~ # drbdadm up drbddemo open(/dev/sda3) failed: Device or resource busy Operation canceled. Command 'drbdmeta 1 v09 /dev/sda3 internal apply-al' terminated with exit code 20 So something is using /dev/sda3 (my drbd partition), but what? -- Per Jessen, Zürich (-8.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Feb 27, 2018 at 5:20 PM, Per Jessen <per@computer.org> wrote:
I need a second pair of eyes. Or a third or a fourth.
I am working on a drbd test setup. Two machines, each has a 2Tb disk, 3 partitions (root, swap, drbd). drbd will eventually be controlled by pacemaker, for now I am just starting and stopping manually. I had drbd working fine, but then I created an lvm PV on /dev/drbd1 and carved out a 10Gb LV.
When I boot up either of the two systems, I see a PV:
office36:~ # pvdisplay WARNING: Device for PV k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW not found or rejected by a filter. WARNING: Device for PV k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW not found or rejected by a filter. --- Physical volume --- PV Name unknown device VG Name Grp1 PV Size 1.77 TiB / not usable 3.52 MiB Allocatable yes PE Size 4.00 MiB Total PE 463093 Free PE 460533 Allocated PE 2560 PV UUID k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW
At this point drbd is not yet running, so there is no /dev/drbd1. I guess lvm start-up sort of gleans the above from /dev/sda3, the drbd partition.
I can't start drbd either -
office36:~ # drbdadm up drbddemo open(/dev/sda3) failed: Device or resource busy Operation canceled. Command 'drbdmeta 1 v09 /dev/sda3 internal apply-al' terminated with exit code 20
So something is using /dev/sda3 (my drbd partition), but what?
lvmetad? Try stopping it. Try explicitly exclude partition from LVM for testing (filter or probably global_filter in case of lvmetad, I suspect filter will case device still be opened but ignored). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Tue, Feb 27, 2018 at 5:20 PM, Per Jessen <per@computer.org> wrote:
I need a second pair of eyes. Or a third or a fourth.
I am working on a drbd test setup. Two machines, each has a 2Tb disk, 3 partitions (root, swap, drbd). drbd will eventually be controlled by pacemaker, for now I am just starting and stopping manually. I had drbd working fine, but then I created an lvm PV on /dev/drbd1 and carved out a 10Gb LV.
When I boot up either of the two systems, I see a PV:
office36:~ # pvdisplay WARNING: Device for PV k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW not found or rejected by a filter. WARNING: Device for PV k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW not found or rejected by a filter. --- Physical volume --- PV Name unknown device VG Name Grp1 PV Size 1.77 TiB / not usable 3.52 MiB Allocatable yes PE Size 4.00 MiB Total PE 463093 Free PE 460533 Allocated PE 2560 PV UUID k2i0DX-Gsao-z8pt-zLDD-Iv4b-qkq1-gGxdoW
At this point drbd is not yet running, so there is no /dev/drbd1. I guess lvm start-up sort of gleans the above from /dev/sda3, the drbd partition.
I can't start drbd either -
office36:~ # drbdadm up drbddemo open(/dev/sda3) failed: Device or resource busy Operation canceled. Command 'drbdmeta 1 v09 /dev/sda3 internal apply-al' terminated with exit code 20
So something is using /dev/sda3 (my drbd partition), but what?
lvmetad? Try stopping it.
Try explicitly exclude partition from LVM for testing (filter or probably global_filter in case of lvmetad, I suspect filter will case device still be opened but ignored).
Thanks Andrei - I already had 'filter' set to only work with /dev/drbd*, but nothing in 'global_filter'. -- Per Jessen, Zürich (-7.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I need a second pair of eyes. Or a third or a fourth.
I am working on a drbd test setup. Two machines, each has a 2Tb disk, 3 partitions (root, swap, drbd). drbd will eventually be controlled by pacemaker, for now I am just starting and stopping manually. I had drbd working fine, but then I created an lvm PV on /dev/drbd1 and carved out a 10Gb LV.
It turns out this was due to "global_filter" not being set in lvm.conf. Without that, lvmetad still looked at /dev/sda3 and found lvm meta data. Now I just need to get pacemaker to run a vgscan -ay after drbd comes up. -- Per Jessen, Zürich (-6.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov -
Per Jessen