My double slash in /proc/mounts experience was as follows:
- trying umount /mnt/target got me two 'not found' lines;
- trying umount.nfs4 /mnt/target got me one 'not found' line;
- workaround: edit /etc/mtab and delete the matching line (even if correct)
then re-run umount.nfs4 /mnt/target.
Other
Two identical error messages on trying to umount an NFS mount as follows :
/export/home/nfshomes was not found in /proc/mounts
/export/home/nfshomes was not found in /proc/mounts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
We get this problem on servers 12.04.5 running Trusty kernel
3.13.0-65-generic (and on 12.04.4 running Quantal kernel 3.5.0-54 )
/etc/fstab has a slash at the start of the NFS server path
/proc/mounts has an unnecessary extra "/" on the NFS path: like this :-
nfs-server://home/users /export/home
uuhhh, probably someone repaired this to bits.
I did a nfs mount using the leading slash (wondering what may be on so.'s mind
to omit it???),
and got into exatly that problem, OS stating "not found in /proc/mounts",
because of different entries there and in /etc/mtab.
But in my case there are two
Same here on 12.04 with kernel 3.2.0-70-generic
--
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://b
Still seeing this on 12.04 with kernel 3.8.0-29-generic
--
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:
h
This did belong in nfs-utils as it provides the (u)mount.nfs4 helpers.
** Package changed: util-linux (Ubuntu) => nfs-utils (Ubuntu)
--
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:
Err
We saw today the same error on our linux boxes after a takeover has been
executed on the netapp heads.
All mountpoints we're visible as "/mountpoint (deleted)" in /proc/mounts
- however the mountpoints were still usable but couldn't be unmounted
without the /etc/mtab workaround (add \040(deleted)
Forgot to inlcude uname -a:
3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:18:19 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
This is also tracked here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711183
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711184
http://bugs.debian.org/cgi-bin/bugrep
Just got hit by the same thing and completely unrelated to comment #4.
We had this with fully formed paths (with slashes) and an NFS server
that went away suddenly. Trying unmount with -f , -l and those two
flags in combination did not solve the issue. When I tried the
suggestion in #7 I found it
This is not a graceful unmount. You still hang if you try to ls/cd the
mount path.
--
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 notificati
I managed to solve the \040(deleted) problem.
Edit the /etc/mtab, add the \040(deleted) to the end of mount path, then
use mount to show the new path. Then you can use the umount.nfs4
"/your/mount/path (deleted)" -f to umount it.
Linux xx 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UT
I'm seeing this too - \040(deleted) added to the end of the entry in
/proc/mounts - the entry there is the only different anywhere else.
I hated the 'hang' you would get with a stale NFS v3 mount but it was a
heck of a lot better than being forced to reboot a server!
What is the workaround for t
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
This problem is not limited to stale mounts.
It's an error in the interaction between mount, umount and mount details
in /proc/mounts vs /etc/mtab
In /etc/mtab, nfs4 mounts seem to have a problem with leading slashes.
For example, on my 12.04 client machine, mounting a zfs volume on a
12.04 host
We just had a similar incident.
The local server autofs mounts a remote NFS. The remote server unexpectidly
powered off (no normal shutdown). The remote server was powered back on however
the local server was not able to access the remote NFS's. It appears the local
server never umounted the rem
I can't imagine why the kernel is deleting a mount point here, stale
mount or otherwise. But it seems to me this is a bug in umount from
util-linux, not in nfs-utils.
** Package changed: nfs-utils (Ubuntu) => util-linux (Ubuntu)
--
You received this bug notification because you are a member of
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => High
--
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 b
This also happens when unmounting a stale NFS share
nas:/raid/www /home/www\040(deleted) nfs4
rw,noatime,vers=4,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=10,sec=sys,clientaddr=192.168.100.11,minorversion=0,local_lock=none,addr=192.168.100.40
0 0
root@back2:~# umount
19 matches
Mail list logo
