File descriptor leaked on lvs invocation ?

[m.ardito]

I have 2 identical pve nodes with

# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

but only on one I get this strange "file descriptor 3 leaked" line invoking lvs:

~# lvs
[B]File descriptor 3 (/usr/share/bash-completion/completions) leaked on lvs invocation. Parent PID 961856: -bash[/B]
  LV            VG                 Attr      LSize  Pool Origin Data%  Move Log Copy%  Convert
  data          pve                -wi-ao--- 33.05g
  root          pve                -wi-ao--- 16.75g
  swap          pve                -wi-ao---  8.38g
...

what can be the cause, what can be different from the other node?

Marco

 

[m.ardito]

don't know, today's gone...

Marco