You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed a pretty strange behaviour on lvm tools inside flatcar.
When running any CSI that uses LVM as backend ( in this case I will show an example using openebs ) in ubuntu, alma, redhat , debian when the CSI creates an LVM to expose a PVC to a pod, lvs and pvs in the host shows that volume just fine. But in flatcar, those new LVM do not show in lvs/pvs in the host neither the used space in the VG is correct. Those information will only be updated in the server is rebooted OR the lvmetad service is restarted.
[ 1 paragraph concisely describing the bug ]
That can mislead sysadmins to change the vg size leading to data corruption because the real state of the volumes are outdated.
( It has happened )
Environment and steps to reproduce
Install flatcar
Add a secondary disk and create a new volumegroup called openebs on it vgcreate openebs /dev/sdb
After the container is up, run sudo lvs or sudo vgs inside the host and you will noticed that the lvs output does not show the newly create logical volume and the vgs output wont show the space used by that volume.
Run sudo systemctl restart lvm2-lvmetad.service OR sudo pvscan --cache or reboot
Try again run lvs or vgs and you will noticed that those outputs now reflect correctly what has been created in openebs
Noticed that the behaviour is only on flatcar, not in any other linux distribution i haved tested ( ubuntu, redhat, alma , debian ).
Expected behavior
Volumes should be shown despite restart lvmetad
The text was updated successfully, but these errors were encountered:
lvmetad has been deprecated and should not be used. The reason it works in other linux distributions like rhel for example is that lvmetad is not present on newer versions.
The solution for flatcar is add this to /etc/lvm/lvm.conf and restart
Description
I have noticed a pretty strange behaviour on lvm tools inside flatcar.
When running any CSI that uses LVM as backend ( in this case I will show an example using openebs ) in ubuntu, alma, redhat , debian when the CSI creates an LVM to expose a PVC to a pod, lvs and pvs in the host shows that volume just fine. But in flatcar, those new LVM do not show in lvs/pvs in the host neither the used space in the VG is correct. Those information will only be updated in the server is rebooted OR the lvmetad service is restarted.
[ 1 paragraph concisely describing the bug ]
That can mislead sysadmins to change the vg size leading to data corruption because the real state of the volumes are outdated.
( It has happened )
Environment and steps to reproduce
vgcreate openebs /dev/sdb
helm install openebs openebs/openebs --set cstor.enabled=false --set nfs-provisioner.enabled=false --set localprovisioner.enabled=false --set zfs-localpv.enabled=false --set lvm-localpv.enabled=true --set ndmOperator.enabled=false --set ndm.enabled=false --namespace kube-system
sudo lvs
orsudo vgs
inside the host and you will noticed that thelvs
output does not show the newly create logical volume and thevgs
output wont show the space used by that volume.sudo systemctl restart lvm2-lvmetad.service
ORsudo pvscan --cache
or rebootNoticed that the behaviour is only on flatcar, not in any other linux distribution i haved tested ( ubuntu, redhat, alma , debian ).
Expected behavior
Volumes should be shown despite restart lvmetad
The text was updated successfully, but these errors were encountered: