[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#582107: marked as done (NFS mounts default to version 4, don't fall back automatically)



Your message dated Fri, 21 May 2010 22:14:02 +0200
with message-id <[🔎] 7ieih5qagl.fsf@lanthane.pps.jussieu.fr>
and subject line Re: Bug#582107: NFS mounts default to version 4, don't fall back automatically
has caused the Debian Bug report #582107,
regarding NFS mounts default to version 4, don't fall back automatically
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 owner@bugs.debian.org
immediately.)


-- 
582107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582107
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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

Attachment: pgpnOpQ6t8Iki.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
>> 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


--- End Message ---

Reply to: