From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-September/018796.html | 111 ++++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-September/018796.html (limited to 'zarb-ml/mageia-dev/2012-September/018796.html') diff --git a/zarb-ml/mageia-dev/2012-September/018796.html b/zarb-ml/mageia-dev/2012-September/018796.html new file mode 100644 index 000000000..c75ecaa4c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-September/018796.html @@ -0,0 +1,111 @@ + + + + [Mageia-dev] Any progress on the NFS mount problem? + + + + + + + + + +

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

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Sep 20 12:59:39 CEST 2012 +

+
+ +
Le 20/09/2012 11:54, Anne Wilson a écrit :
+>> and -v option to mount.nfs on client side to get more verbose error
+>> reporting.
+>>
+>
+> How do I do that?  mount.nfs is an executable, not a shell script, so
+> I can't add it there.  Attempting to add it in the mount command says
+> it is an invalid option.
+This is probably an issue with arguments order in command line parsing. 
+Try either of those command (they are strictly equivalent):
+mount -v -t nfs 192.168.0.40:/Data1 /mnt/borg2_Data1
+mount.nfs -v 192.168.0.40:/Data1 /mnt/borg2_Data1
+
+If that doesn't work, check their man page for exact syntax.
+
+Also, you can check available NFS version on your servers:
+rpcinfo -s 192.168.0.40
+rpcinfo -s 192.168.0.200
+
+-- 
+BOFH excuse #136:
+
+Daemons loose in system.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1