Comment 9 for bug 591823

I certainly don't get this error running lvs alone.

I suspect lvs is reporting these issues coming from various programs as it discovers open fds when called; if you're seeing this with bash, check your startup files or environment (e.g. it could be left open by your display manager, window manager, session manager or whatever is in the tree of processes launching your shell). You can see open files by poking /proc/<pid>/fd/*