Hide Forgot
[root@brick1 ~]# ls -l /proc/30418/fd total 0 lrwx------ 1 root root 64 Aug 26 18:33 0 -> /dev/null lrwx------ 1 root root 64 Aug 26 18:33 1 -> /dev/null lrwx------ 1 root root 64 Aug 26 18:33 10 -> /export/export lrwx------ 1 root root 64 Aug 26 18:33 11 -> /export/export/ubuntu1/ubuntu1-flat.vmdk lrwx------ 1 root root 64 Aug 26 18:33 12 -> /export/export/ubuntu1/.lck-0c000001b30e0000 lrwx------ 1 root root 64 Aug 26 18:33 13 -> /export/export/ubuntu1/.lck-14000001b30e0000 lrwx------ 1 root root 64 Aug 26 18:33 2 -> /dev/null lrwx------ 1 root root 64 Aug 26 18:33 3 -> anon_inode:[eventpoll] l-wx------ 1 root root 64 Aug 26 18:33 4 -> /share/kris/install/var/log/glusterfs/share-kris-volfiles-vmstore-export1.vol.log lr-x------ 1 root root 64 Aug 26 18:33 5 -> /share/kris/volfiles/vmstore/export1.vol lrwx------ 1 root root 64 Aug 26 18:33 6 -> socket:[61096] l-wx------ 1 root root 64 Aug 26 18:33 7 -> pipe:[61092] lrwx------ 1 root root 64 Aug 26 18:33 8 -> socket:[72015] lrwx------ 1 root root 64 Aug 26 18:33 9 -> socket:[72018] [root@brick1 ~]# lrwx------ 1 root root 64 Aug 26 18:33 10 -> /export/export indicates that there is still dir fd leak on the export dir. This happens sometimes when nfs server is restarted.
What changes/happens between the first and second ls? nfs server restart?
not able to reproduce it. Most certainly fixed as part of the fd leaks fixes for 1397.