I think the remote volume with/without leading slash is different to the \040(deleted) problem. I have a machine in the latter state:
# grep monster3 /etc/mtab 192.168.6.117:/share /media/monster3 nfs4 rw,noatime,addr=192.168.6.117,clientaddr=192.168.6.110 0 0 # grep monster3 /proc/mounts 192.168.6.117:/share /media/monster3\040(deleted) nfs4 rw,noatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.6.110,minorversion=0,local_lock=none,addr=192.168.6.117 0 0 # umount /media/monster3 /media/monster3 was not found in /proc/mounts /media/monster3 was not found in /proc/mounts root@proliant:~# umount /media/monster3 root@proliant:~# umount "/media/monster3 " umount: /media/monster3 : not found root@proliant:~# umount "/media/monster3 (deleted)" umount: /media/monster3 (deleted): not found I tried some variations of editing what's in /etc/mtab, adding \040 or \040(deleted), and variations of what I pass to umount, to no avail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974374 Title: Error on unmounting a NFSv4 share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/974374/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
