Re: lvm commands hanging when run from inside a kubernetes pod
Demi Marie Obenour <[email protected]>
| Newsgroups | gmane.linux.lvm.general |
|---|---|
| Message-ID | <YpcUpGsiSjwK8cG2@itl-email> |
On Wed, Jun 01, 2022 at 12:20:32AM +0530, Abhishek Agarwal wrote: > Hi Roger. Thanks for your reply. I have rerun the command with `strace -f` > as you suggested. Here is the pastebin link containing the detailed output > of the command: https://pastebin.com/raw/VRuBbHBc Even if you can get LVM “working”, it is still likely to cause data corruption at some point, as there is no guarantee that different LVM processes in different namespaces will see each others’ locks. Why do you need to run LVM in a container? What are you trying to accomplish? -- Sincerely, Demi Marie Obenour (she/her/hers) Invisible Things Lab _______________________________________________ linux-lvm mailing list [email protected] https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmKXFKQACgkQsoi1X/+c IsHgrA/9GHro+IAfeKojAEFwUeftqtjaPCyIuIDy+kHLYQzMJaBDTrxJJEU/lDnK 9Swf/F5M4wK3eEumDfWjSYLIZIR2TBIdtrgp63icLvsuu9urz0TJwhl/v+0F6Z2U EiKGSOJz5wjWonJmwH/5GKE/ipvhEvEpaWD1Ai8XzDx3HbgHM0VjvLFDEXnebyiq OZ5SkrWn1ch61kvyMAyqKZA7hnvuscGY9XFHnGR1moa+8W3karETMbA5SNEasLuM Sje5UDqIdOCNe2AzPZkKsrXlafBCSZE8+hEPuIaJfVyBArxqB7fLx/3EoGfQI7GN Jr3jro9/N7SoA7ZxWpcp/NLnPs36e7RA5Pl2VIEkRSlpbEowk2PNWN1JTqPqIBE/ TrA8VB95D7DYkKeGx1GgzXnszjePUX0CsJ0sJNxdWJ+BkE/5UkrxL4FM1mVOyzRJ l8xGD2cjjizHrcmacILY7PkBASnRgzSlQGeVvmS2F2JO7mVrkkBQwx335hGCuxnG SwnWqFRqc+x8z+rZV7zm5L3lm5BBiP8WQqAmi91QGoZ8DTv9ppO/HUOIYJp1pjH5 jSPoVHIqG5lMb07hphIOm6YUkD12jzZWy7QR/TM25t9uN+3G9mC8g7aOm0G7Whu7 elei9i6ZiEKYEFIBC3Nm2exKcHq8rc4QfClUbjNCrhEflUclzYY= =0lv/ -----END PGP SIGNATURE-----