On volume activation lvm uses mlock() in a way that fails on musl. Changing the /activation/use_mlockall setting to 1 helps avoid these messages. The error messages are purely cosmetic - the volumes get activated anyway - but can be confusing. Reproducible: Always Steps to Reproduce: 1. vgchange -ay Actual Results: # vgchange -ay /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. 7f9f434c2000-7f9f43702000 r-xp 00000000 fd:00 71554 /lib/libdevmapper.so.1.02: mlock failed: Out of memory 7f9f43707000-7f9f4390c000 r-xp 00000000 fd:00 71679 /lib/libdevmapper-event.so.1.02: mlock failed: Out of memory 2 logical volume(s) in volume group "scylla" now active Expected Results: # vgchange -ay /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. 2 logical volume(s) in volume group "scylla" now active Providing a git-formatted patch for inclusion in hardened-dev:musl
Created attachment 403812 [details, diff] 0001-Change-the-default-setting-of-use_mlockall-on-musl.patch
(In reply to Robert Sebastian Gerus from comment #1) > Created attachment 403812 [details, diff] [details, diff] > 0001-Change-the-default-setting-of-use_mlockall-on-musl.patch I'm not against this patch, but its a workaround and not a fix.
This patch http://git.alpinelinux.org/cgit/aports/tree/main/lvm2/mallinfo.patch?id=42039c543f4af10ab8f79253e0f48f33592ee533 from Alpine Linux seems to be related.
