Package: nfs-common
Version: 1:1.2.2-1

Recent versions of mount.nfs default to NFS version 4. The result is
that mounting ordinary version 3 filesystems fails with EPERM.

The bug is not the new default, which is open to debate; the bug is that
Sun RPC is supposed to allow negotiation of the protocol version, and
that mount appears unable to fall back to version 3 if version 4 is not
supported by the server.

A workaround is to add "vers=3" to the options column in /etc/fstab.

--jch

On Tue, 2010-05-18 at 14:23 +0200, Juliusz Chroboczek wrote:
> Package: nfs-common
> Version: 1:1.2.2-1
>
> Recent versions of mount.nfs default to NFS version 4.

My understanding is that mount.nfs does not even support version 4 and
you have to explicitly use mount.nfs4 (i.e. specify filesystem type as
'nfs4').

> The result is that mounting ordinary version 3 filesystems fails with EPERM.

I can't reproduce this.

> The bug is not the new default, which is open to debate; the bug is that
> Sun RPC is supposed to allow negotiation of the protocol version, and
> that mount appears unable to fall back to version 3 if version 4 is not
> supported by the server.
>
> A workaround is to add "vers=3" to the options column in /etc/fstab.

Please provide the complete fstab line that fails for you.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

>> The result is that mounting ordinary version 3 filesystems fails with EPERM.
>
> I can't reproduce this.

Neither can I -- it now appears to work without the vers=3. Sorry for the noise.

Juliusz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 7ieih5qagl.fsf@lanthane.pps.jussieu.fr">http://lists.debian.org/7ieih5qagl.fsf@lanthane.pps.jussieu.fr