<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Any progress on the NFS mount problem?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F&In-Reply-To=%3C505AE7BF.7070200%40kde.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018788.html">
<LINK REL="Next" HREF="018796.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Any progress on the NFS mount problem?</H1>
<B>Anne Wilson</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F&In-Reply-To=%3C505AE7BF.7070200%40kde.org%3E"
TITLE="[Mageia-dev] Any progress on the NFS mount problem?">annew at kde.org
</A><BR>
<I>Thu Sep 20 11:54:07 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018788.html">[Mageia-dev] Any progress on the NFS mount problem?
</A></li>
<LI>Next message: <A HREF="018796.html">[Mageia-dev] Any progress on the NFS mount problem?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18793">[ date ]</a>
<a href="thread.html#18793">[ thread ]</a>
<a href="subject.html#18793">[ subject ]</a>
<a href="author.html#18793">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 19/09/12 21:47, Guillaume Rousse wrote:
><i> Le 19/09/2012 19:46, Anne Wilson a écrit :
</I>>><i> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
</I>>><i>
</I>>><i> My laptop uses fstab lines to mount directories on the old server
</I>>><i> and also on a QNAS box. I've no idea what version of Linux is
</I>>><i> running on the QNAS, but the mounts are working there. The old
</I>>><i> server is running Mageia 2, and mount to that don't work.
</I>>><i>
</I>>><i> Working line example:
</I>>><i>
</I>>><i> 192.168.0.200:/DataFromBorg2 /mnt/QNAS-Borg2-Data nfs
</I>>><i> user,timeo=14 0 0
</I>>><i>
</I>>><i> Non-working (M2) example:
</I>>><i>
</I>>><i> 192.168.0.40:/Data1 /mnt/borg2_Data1 nfs
</I>>><i> user,rsize=8192,wsize=8192,nosuid,soft 0 0
</I>><i> First, your are clearly not mounting the same path (/DataFromBorg2
</I>><i> vs /Data1), so your comparaison is quite biased.
</I>><i>
</I>As I stated, these are two different sources, the old server and the
new one. The version used in the QNAS mount is the one I had
previously used with Scientific Linux, so that's where I started from.
I gave this information because it proves that the nfs client is at
least working since it can connect with the QNAS, so the problem is in
how I connect with the nfs server on borg2.
><i> Second, you'd rather use mount command, than hardcoded entries in
</I>><i> /etc/fstab entries, to debug the issues. You'll get much more
</I>><i> input.
</I>><i>
</I>I've had no success at all there - I never fully understood command
mounting.
mount 192.168.0.40:/Data1 /mnt/borg2_Data1 -t nfs
mount.nfs: requested NFS version or transport protocol is not supported
Every variation I've tried on the command simply returns to the help file.
><i> Third, you'd rather avoid useless options such as rsize and wsize,
</I>><i> unless you know what you're doing.
</I>><i>
</I>First, that is a format I used in earlier versions/distros. Second,
it was copied from a bug report. In the absence of better advice, I
took that.
>><i> Note that I initially wrote it the same way as the QNAS line,
</I>>><i> and reverted to this older style when I found that didn't work.
</I>>><i>
</I>>><i> mount -a gives mount.nfs: requested NFS version or transport
</I>>><i> protocol is not supported
</I>>><i>
</I>>><i> If I forget and click on the mount point in Dolphin I get
</I>>><i>
</I>>><i> "An error occurred while accessing 'Data1 on 192.168.0.40', the
</I>>><i> system responded: mount.nfs: requested NFS version or transport
</I>>><i> protocol is not supported"
</I>>><i>
</I>>><i> Is this <A HREF="https://bugs.mageia.org/show_bug.cgi?id=6541?">https://bugs.mageia.org/show_bug.cgi?id=6541?</A> And is
</I>>><i> there anything I can do to improve matters?
</I>><i> According to the error message, you have probably a version
</I>><i> negotiation issue between your client and your server. Add -d
</I>><i> option to rpc.mountd (RPCMOUNTDOPTS variable in /etc/sysconfig/nfs)
</I>><i> on server side,
</I>
Done.
><i> and -v option to mount.nfs on client side to get more verbose error
</I>><i> reporting.
</I>><i>
</I>
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.
Which log file should I be monitoring for this? I issued a "mount -a"
command then checked dmesg, messages and syslog, and none of them are
reporting anything at all about a mount attempt.
Anne
- --
Need KDE help? Try
<A HREF="http://userbase.kde.org">http://userbase.kde.org</A> or
<A HREF="http://forum.kde.org">http://forum.kde.org</A>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAlBa57YACgkQj93fyh4cnBcSMwCeKPZaOnZkTahtR6ghQp+nuIu8
OUIAn33twD0NPh2Pksa66oK9c1fUN8Rd
=7fLC
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018788.html">[Mageia-dev] Any progress on the NFS mount problem?
</A></li>
<LI>Next message: <A HREF="018796.html">[Mageia-dev] Any progress on the NFS mount problem?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18793">[ date ]</a>
<a href="thread.html#18793">[ thread ]</a>
<a href="subject.html#18793">[ subject ]</a>
<a href="author.html#18793">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>