Dne 27. 05. 22 v 9:02 Abhishek Agarwal napsal(a):
When a kubernetes pod is scheduled on the node having lvm2 libraries already
installed and trying to run lvm commands using those node binaries from inside
the pod container, the commands hang and are waiting on something to complete.
Although when ctrl+c is pressed the terminal session resumes and checking the
final code for the execution returns a "0" error code and the commands
operation is also carried out successfully.
lvm2 is *NOT* designed to be executed in/from a container.
It cannot work properly as it directly communicates with system's udevd -
which you likely don't have running in your container.
You could kind of 'fake it' by running lvm2 wihout udev synchronization - but
this will just open another cave of other problems (missing synchronization).
So your lvm2 command should be always executed on your hosting machine
(since it does control resources without containerization support - like
devices) and then you should 'pass' created LV to your container in some way.
Regards
Zdenek
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
