Bug#653630: /sbin/mount.nfs: Re: nfs-common: Only root can unmount, nautilus badly confused
On 01/22/2012 01:53 PM, Roger Leigh wrote:
> On Sun, Jan 22, 2012 at 12:34:39PM +0000, Roger Leigh wrote:
>> On Sun, Jan 22, 2012 at 12:55:45PM +0100, Michael Biebl wrote:
>>> On 22.01.2012 12:30, Luk Claes wrote:
>>>>> -- /etc/fstab --
>>>>> liveserv:/mnt/library /mnt/library nfs noauto,user 0 0
>>>>> -- /proc/mounts --
>>>>> liveserv:/mnt/library/ /mnt/library nfs rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.104,mountvers=3,mountport=46570,mountproto=udp,local_lock=none,addr=192.168.1.104 0 0
>>> I am missing a bit of context here. Is the problem related to the "user"
>>> option or regarding a trailing "/"?
>>> wrt /etc/mtab being a symlink to /proc/mounts: I assume mount.nfs is
>>> built against libmount, seeing  as fixed? Do you get a file
>>> /run/mount/utab when the nfs share is mounted? What does it contain?
>> I'm afraid I can't help with the specifics immediately (I'll need
>> to set up some NFS mounts), but some general comments about the
>> recent changes:
>> - if you mount a filesystem with the "user" option, the user who
>> mounted it will be written to /run/mount/utab. While I've not
>> tested this for NFS, it's certainly the case for all other mounts.
> A quick test with NFS4 showed that /run/mount/utab does not contain
> anything, and additionally it looks like mount.nfs4 is /not/ linked
> against libmount, which I thought (perhaps mistakenly, unless it's
> a regression) was now using libmount.
> NFS certainly does support libmount, it's right there in the
> configure script. Looks like it just needs adding to the Build-Deps
> and enabling in debian/rules by configuring with
> --enable-libmount-mount. I would highly recommend that the nfs-common
> enable this as soon as possible!
Hmm, apparently there was some confusion from my part: I did not expect
to have to explicitly build depend on libmount-dev as libblkid-dev has a
similar description I thought one would replace the other. I also did
not expect I had to explicitly enable libmount via configure as
configure has default --enable-mount=yes and --enable-libmount-mount
same as --enable-mount. Apparently only when explicitly setting
--enable-mount=yes, it would also be set for --enable-libmount-mount.
Anyway, I have explicitly enabled it now (and added the build dependency).
Pavel: Can you have a look if the new version from unstable fixes your
problem (this bug)?