Bug#653630: marked as done (nfs-common: Only root can unmount, nautilus badly confused)
Your message dated Sun, 22 Jan 2012 23:17:01 +0100
with message-id <4F1C8ADD.email@example.com>
and subject line Re: Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused
has caused the Debian Bug report #653630,
regarding nfs-common: Only root can unmount, nautilus badly confused
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
This seems similar to #572406 but for me the user and users options are
both broken, and there are further problems with managing the mount with
nautilus which I'll describe later.
With the users option I can mount the remote FS but umount fails:
umount.nfs4: You are not permitted to unmount /media/htpc
I tried nfsvers=3 and the error message changed to:
umount: /media/htpc mount disagrees with the fstab
but umount succeeded as root.
With user instead of users the error message is:
umount: only root can unmount htpc.local:/home/tony from /media/htpc
The mount points show up under "Devices" in nautilus' sidebar, but if I
click one I get the error, "Timeout waiting for mount to appear". This
quite often used to happen, but in fact the mount would be successful
and by clicking it again I could access it as normal. However, now
nautilus does not recognise it as being mounted but clicking it again
gives an "already mounted" error instead of opening the directory.
Conversely, if I restart nautilus with the mount already mounted, it
does recognise it as mounted and adds an eject icon. But the eject
doesn't work and it also doesn't disappear if I unmount it from the
command line. My nautilus version is 3.2.1-2+b1.
-- Package-specific info:
-- rpcinfo --
program vers proto port
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 33343 status
100024 1 tcp 43033 status
-- /etc/default/nfs-common --
-- /etc/idmapd.conf --
Verbosity = 0
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Nobody-User = nobody
Nobody-Group = nogroup
-- /etc/fstab --
htpc.local:/home/tony /media/htpc nfs user,noauto,nolock,nfsvers=4 0 0
infant.local:/home/tony /media/infant nfs user,noauto,nolock,nfsvers=4 0 0
tiber.local:/home/tony /media/tiber nfs user,noauto,nolock,nfsvers=4 0 0
-- /proc/mounts --
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nfs-common depends on:
ii adduser 3.113
ii initscripts 2.88dsf-18
ii libc6 2.13-24
ii libcap2 1:2.22-1
ii libcomerr2 1.42-1
ii libdevmapper1.02.1 2:1.02.67-2
ii libevent-2.0-5 2.0.16-stable-1
ii libgssapi-krb5-2 1.10+dfsg~alpha2-1
ii libgssglue1 0.3-4
ii libk5crypto3 1.10+dfsg~alpha2-1
ii libkeyutils1 1.5.2-2
ii libkrb5-3 1.10+dfsg~alpha2-1
ii libnfsidmap2 0.25-1
ii libtirpc1 0.2.2-5
ii libwrap0 7.6.q-22
ii lsb-base 3.2-28
ii rpcbind 0.2.0-7
ii ucf 3.0025+nmu2
Versions of packages nfs-common recommends:
ii python 2.7.2-9
nfs-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 01/22/2012 11:14 PM, Pavel Yakunin wrote:
>> Can you test if it fixes the bug, thanks already?
> I've obtained the new version. Now everything is all right,
> Thanks a lot.
Ok, closing this bug.
--- End Message ---