[Mageia-dev] Any progress on the NFS mount problem?

Wed Sep 19 22:47:46 CEST 2012

Le 19/09/2012 19:46, Anne Wilson a écrit :
+> -----BEGIN PGP SIGNED MESSAGE-----
+> Hash: SHA1
+>
+> My laptop uses fstab lines to mount directories on the old server and
+> also on a QNAS box.  I've no idea what version of Linux is running on
+> the QNAS, but the mounts are working there.  The old server is running
+> Mageia 2, and mount to that don't work.
+>
+> Working line example:
+>
+> 192.168.0.200:/DataFromBorg2 /mnt/QNAS-Borg2-Data nfs user,timeo=14 0 0
+>
+> Non-working (M2) example:
+>
+> 192.168.0.40:/Data1 /mnt/borg2_Data1 nfs
+> user,rsize=8192,wsize=8192,nosuid,soft 0 0
+First, your are clearly not mounting the same path (/DataFromBorg2 vs 
+/Data1), so your comparaison is quite biased.
+
+Second, you'd rather use mount command, than hardcoded entries in 
+/etc/fstab entries, to debug the issues. You'll get much more input.
+
+Third, you'd rather avoid useless options such as
+rsize and wsize, unless you know what you're doing.
+
+> Note that I initially wrote it the same way as the QNAS line, and
+> reverted to this older style when I found that didn't work.
+>
+> mount -a gives
+> mount.nfs: requested NFS version or transport protocol is not supported
+>
+> If I forget and click on the mount point in Dolphin I get
+>
+> "An error occurred while accessing 'Data1 on 192.168.0.40', the system
+> responded: mount.nfs: requested NFS version or transport protocol is not
+> supported"
+>
+> Is this https://bugs.mageia.org/show_bug.cgi?id=6541?  And is there
+> anything I can do to improve matters?
+According to the error message, you have probably a version negotiation 
+issue between your client and your server. Add -d option to rpc.mountd 
+(RPCMOUNTDOPTS variable in /etc/sysconfig/nfs) on server side, and -v 
+option to mount.nfs on client side to get more verbose error reporting.
+
+-- 
+BOFH excuse #275:
+
+Bit rot
+