Bug#774762: try harder to find reasons for failed `lvchange -an` by looking at /proc/*/mountinfo

[chrysn]

> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20150113/7b35c5c4/attachment.sig>