> I'd say the best "who-uses" tool in this case is "lsblk" [...] > >LVM itself already uses this tool within helper "blkdeactivate" script >[...]
so you see a chance that lvm could delegate the diagnoistic messages for where to find the offending mount point to lsblk (or dmsetup or findmnt, but lsblk is probably the most suitable of those)? if yes, i'd open a similar bug against util-linux (lsblk does not do any better than lvm in container conditions at the moment), and keep this only open to track lvm's progress on delegating to lsblk. best regards chrysn
signature.asc
Description: Digital signature
