-
Bug
-
Resolution: Done
-
Normal
-
None
-
rhel-10.0
-
None
-
Yes
-
Important
-
rhel-storage-lvm
-
ssg_filesystems_storage_and_HA
-
5
-
False
-
False
-
-
None
-
None
-
None
-
None
-
-
x86_64
-
None
This scenario seemed to work fine in RHEL9. This scenario takes a local VG with a thinpool and virt volumes and converts it to a shared sanlock VG.
sanlock-3.9.5-2.el10 BUILT: Wed Oct 23 04:04:35 PM EST 2024
sanlock-lib-3.9.5-2.el10 BUILT: Wed Oct 23 04:04:35 PM EST 2024
kernel-6.11.0-25.el10 BUILT: Mon Sep 16 04:27:55 PM EST 2024
lvm2-2.03.27-1.el10 BUILT: Fri Oct 4 12:02:18 PM EST 2024
lvm2-libs-2.03.27-1.el10 BUILT: Fri Oct 4 12:02:18 PM EST 2024
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdb1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sde1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdd1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdg1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdh1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdf1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdc1
megatest-23.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sda1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdb1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sde1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdd1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdg1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdh1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdf1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sdc1
megatest-24.lab.eng.rdu2.redhat.com: lvmdevices -y --adddev /dev/sda1
Refreshing storage view due to potential lvmlockd metadata checksums after dicing
Running lvmlockd with sanlock, setting up global lock VG.
vgcreate --shared global /dev/sda1
megatest-23.lab.eng.rdu2.redhat.com: vgchange --lock-start global
megatest-24.lab.eng.rdu2.redhat.com: vgchange --lock-start global
Device /dev/sda1 has PVID ZZtA12wvILxPDeRhTyb7jgdS8IJb9psK (devices file none)
creating lvm devices...
megatest-23.lab.eng.rdu2.redhat.com: pvcreate --config devices/scan_lvs=1 /dev/sdc1 /dev/sdf1 /dev/sdh1 /dev/sdg1 /dev/sdd1
megatest-23.lab.eng.rdu2.redhat.com: vgcreate --config devices/scan_lvs=1 --shared snapper_thinp /dev/sdc1 /dev/sdf1 /dev/sdh1 /dev/sdg1 /dev/sdd1
megatest-23.lab.eng.rdu2.redhat.com: vgchange --lock-start snapper_thinp
megatest-24.lab.eng.rdu2.redhat.com: vgchange --lock-start snapper_thinp
Device /dev/sdd1 has PVID nH6S6aobQ2rHMI9usnRRPcWrNuZUfe6y (devices file none)
Device /dev/sdg1 has PVID Ac5ljFhhdLbmHnl2afh9OQlFG9KpMuIF (devices file none)
Device /dev/sdh1 has PVID gtBCuCYFdX6hOWkeGnzeCmJ3BZm6vVq0 (devices file none)
Device /dev/sdf1 has PVID FgGzxlPtJCB6SOtICGtf6QSKNBdq0Va7 (devices file none)
Device /dev/sdc1 has PVID rkA7T01sqngAb2wKrBCncddnoFGE687W (devices file none)
============================================================
Iteration 1 of 1 started at Wed Oct 30 10:55:27 AM EST 2024
============================================================
SCENARIO - [convert_thin_snap_to_shared]
Convert a local VG containing thin pool volumes to a shared VG
megatest-24.lab.eng.rdu2.redhat.com: vgchange --lock-stop snapper_thinp
verifying sanlock lock stoppage of snapper_thinp on megatest-24.lab.eng.rdu2.redhat.com
vgremove -y snapper_thinp
vgcreate snapper_thinp /dev/sdc1 /dev/sdd1 /dev/sdf1 /dev/sdg1 /dev/sdh1
Making pool volume
lvcreate --yes --activate ey --thinpool POOL -L 1G --profile thin-performance --zero n --poolmetadatasize 4M snapper_thinp
Making origin volume
lvcreate --yes --activate ey --virtualsize 1G -T snapper_thinp/POOL -n origin
lvcreate --yes --activate ey --virtualsize 1G -T snapper_thinp/POOL -n other1
WARNING: Sum of all thin volume sizes (2.00 GiB) exceeds the size of thin pool snapper_thinp/POOL (1.00 GiB).
lvcreate --yes --activate ey -V 1G -T snapper_thinp/POOL -n other2
WARNING: Sum of all thin volume sizes (3.00 GiB) exceeds the size of thin pool snapper_thinp/POOL (1.00 GiB).
lvcreate --yes --activate ey -V 1G -T snapper_thinp/POOL -n other3
WARNING: Sum of all thin volume sizes (4.00 GiB) exceeds the size of thin pool snapper_thinp/POOL (1.00 GiB).
lvcreate --yes --activate ey -V 1G -T snapper_thinp/POOL -n other4
WARNING: Sum of all thin volume sizes (5.00 GiB) exceeds the size of thin pool snapper_thinp/POOL (1.00 GiB).
lvcreate --yes --activate ey --virtualsize 1G -T snapper_thinp/POOL -n other5
WARNING: Sum of all thin volume sizes (6.00 GiB) exceeds the size of thin pool snapper_thinp/POOL (1.00 GiB).
lvcreate --yes --activate ey -k n -s /dev/snapper_thinp/origin -n to_shared
vgchange -an snapper_thinp
vgchange --lock-type sanlock snapper_thinp
WARNING: Sum of all thin volume sizes (7.00 GiB) exceeds the size of thin pools (1.00 GiB).
_init_lv_sanlock lvmlockd result -22
Cannot allocate lock for new LV.
unable to convert volume group to shared
[root@megatest-23 ~]# systemctl status sanlock
â— sanlock.service - Shared Storage Lease Manager
Loaded: loaded (/usr/lib/systemd/system/sanlock.service; disabled; preset: disabled)
Active: active (running) since Wed 2024-10-30 10:44:02 EST; 21min ago
Invocation: 93c002104df3430ba68c683fd501a6f4
Process: 4388 ExecStart=/usr/sbin/sanlock daemon (code=exited, status=0/SUCCESS)
Main PID: 4393 (sanlock)
Tasks: 7 (limit: 100464)
Memory: 31.5M (peak: 34M)
CPU: 782ms
CGroup: /system.slice/sanlock.service
â"œâ"€4393 /usr/sbin/sanlock daemon
â""â"€4394 /usr/sbin/sanlock daemon
Oct 30 10:44:02 megatest-23.lab.eng.rdu2.redhat.com systemd[1]: Starting sanlock.service - Shared Storage Lease Manager...
Oct 30 10:44:02 megatest-23.lab.eng.rdu2.redhat.com systemd[1]: Started sanlock.service - Shared Storage Lease Manager.
Oct 30 10:44:02 megatest-23.lab.eng.rdu2.redhat.com sanlock[4393]: sanlock daemon started 3.9.5 host a4ba12ad-b627-4a80-9f96-890ab883ec73.megatest-23 (megatest-23.lab.eng.rdu2.redhat.com)
[root@megatest-23 ~]# systemctl status lvmlockd
â— lvmlockd.service - LVM lock daemon
Loaded: loaded (/usr/lib/systemd/system/lvmlockd.service; disabled; preset: disabled)
Active: active (running) since Wed 2024-10-30 10:44:23 EST; 20min ago
Invocation: 33a81e3a39324e989e7407de225c5a33
Docs: man:lvmlockd(8)
Main PID: 4416 (lvmlockd)
Tasks: 4 (limit: 100464)
Memory: 18.4M (peak: 19.2M)
CPU: 70ms
CGroup: /system.slice/lvmlockd.service
â""â"€4416 /usr/sbin/lvmlockd --foreground
Oct 30 10:44:23 megatest-23.lab.eng.rdu2.redhat.com systemd[1]: Starting lvmlockd.service - LVM lock daemon...
Oct 30 10:44:23 megatest-23.lab.eng.rdu2.redhat.com (lvmlockd)[4416]: lvmlockd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Oct 30 10:44:23 megatest-23.lab.eng.rdu2.redhat.com lvmlockd[4416]: [D] creating /run/lvm/lvmlockd.socket
Oct 30 10:44:23 megatest-23.lab.eng.rdu2.redhat.com lvmlockd[4416]: 1730303063 lvmlockd started
Oct 30 10:44:23 megatest-23.lab.eng.rdu2.redhat.com systemd[1]: Started lvmlockd.service - LVM lock daemon.
Oct 30 10:56:23 megatest-23.lab.eng.rdu2.redhat.com lvmlockd[4416]: 1730303783 init_lv no lockspace found