summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-October/019098.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-October/019098.html')
-rw-r--r--zarb-ml/mageia-dev/2012-October/019098.html130
1 files changed, 130 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-October/019098.html b/zarb-ml/mageia-dev/2012-October/019098.html
new file mode 100644
index 000000000..c6eae9bf6
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-October/019098.html
@@ -0,0 +1,130 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Any progress on the NFS mount problem? - One step further
+ </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%20-%20One%20step%0A%20further&In-Reply-To=%3C5069D6C1.1040008%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="019092.html">
+ <LINK REL="Next" HREF="019099.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Any progress on the NFS mount problem? - One step further</H1>
+ <B>Guillaume Rousse</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Any%20progress%20on%20the%20NFS%20mount%20problem%3F%20-%20One%20step%0A%20further&In-Reply-To=%3C5069D6C1.1040008%40gmail.com%3E"
+ TITLE="[Mageia-dev] Any progress on the NFS mount problem? - One step further">guillomovitch at gmail.com
+ </A><BR>
+ <I>Mon Oct 1 19:45:37 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="019092.html">[Mageia-dev] Any progress on the NFS mount problem? - One step further
+</A></li>
+ <LI>Next message: <A HREF="019099.html">[Mageia-dev] Any progress on the NFS mount problem? - One step further
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19098">[ date ]</a>
+ <a href="thread.html#19098">[ thread ]</a>
+ <a href="subject.html#19098">[ subject ]</a>
+ <a href="author.html#19098">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 01/10/2012 17:26, Anne Wilson a &#233;crit :
+&gt;<i> -----BEGIN PGP SIGNED MESSAGE-----
+</I>&gt;<i> Hash: SHA1
+</I>&gt;<i>
+</I>&gt;<i> On Monday 01 Oct 2012 13:18:36 Guillaume Rousse wrote:
+</I>&gt;&gt;<i> Le 22/09/2012 21:16, Anne Wilson a &#233;crit :
+</I>&gt;&gt;&gt;<i> udp 0 0 *:nfs *:*
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> unfsd
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Ouch... You're running an obsolete alternative nfs server. You
+</I>&gt;&gt;<i> should uninstall the unfs3 package, and this package should get
+</I>&gt;&gt;<i> removed
+</I>&gt;<i> from
+</I>&gt;&gt;<i> the distribution.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> To summarize, here are the mandatory steps: - check you have
+</I>&gt;&gt;<i> nfs-utils-clients installed on clients - check you have
+</I>&gt;&gt;<i> nfs-utils-clients and nfs-utils installed on server - check
+</I>&gt;&gt;<i> rpcbind, and nfs-common services are running on clients - check
+</I>&gt;&gt;<i> rpcbind, nfs-common and nfs-server services are running on
+</I>&gt;<i> the
+</I>&gt;&gt;<i> server
+</I>&gt;&gt;<i>
+</I>&gt;<i> Not sure of the command-line for checking things that don't respond to
+</I>&gt;<i> &quot;service whatever status&quot;, but MCC says all those services are running
+</I>&gt;<i> on the server.
+</I>MCC won't give any useful detail, &quot;service nfs-common status&quot; will...
+
+[..]
+&gt;&gt;<i> Now, to ensure usage of NFSv4 instead of obsolete NFSv3: - check
+</I>&gt;&gt;<i> every host is configured to run rpc.idmapd, meaning NEED_IDMAPD=yes
+</I>&gt;&gt;<i> in /etc/sysconfig/nfs-common
+</I>&gt;<i>
+</I>&gt;<i> Done
+</I>&gt;<i>
+</I>&gt;&gt;<i> - check your server export a root filesystem, using fsid=0 options
+</I>&gt;&gt;<i> in its /etc/exports configuration file
+</I>&gt;<i>
+</I>&gt;<i> Added that - how do I tell it to ignore the old exports and act on
+</I>&gt;<i> those in /etc/exports? I can't find my notes about that.
+</I>Quick answer: service nfs-server restart
+
+&gt;&gt;<i> - drop all your legacy nfs options, such as wsize and rsize from
+</I>&gt;&gt;<i> your mount options
+</I>&gt;&gt;<i>
+</I>&gt;<i> Done - the lines now match the working QNAS mounts, eg
+</I>&gt;<i>
+</I>&gt;<i> 192.168.0.40:/home /mnt/borg2/home nfs user,timeo-14 0 0
+</I>Why do you need a timeout, and why 14s ? If you're not an NFS expert,
+you'd better rely on default values only.
+
+Also, take cares, with NFSv4, you don't mount the actual server
+filepath, but the exported filepath: the root filesystem (the one with
+fsid=0) will be available as /, whatever its actual path.
+
+Once again, test everything manually with manual mount command before
+hardcoding them in /etc/fstab.
+
+&gt;&gt;<i> Last, you'd better use autofs to mount those filesystems on
+</I>&gt;&gt;<i> demand, rather than hardcoding them in /etc/fstab, which avoid to
+</I>&gt;&gt;<i> relies on server availability during the boot.
+</I>&gt;<i>
+</I>&gt;<i> Replace nfs with autofs in those lines?
+</I>No, that means dropping any nfs filesystem entry in your /etc/fstab, and
+configuring autofs daemon instead. But that's off-topic right now...
+
+--
+BOFH excuse #260:
+
+We're upgrading /dev/null
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="019092.html">[Mageia-dev] Any progress on the NFS mount problem? - One step further
+</A></li>
+ <LI>Next message: <A HREF="019099.html">[Mageia-dev] Any progress on the NFS mount problem? - One step further
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19098">[ date ]</a>
+ <a href="thread.html#19098">[ thread ]</a>
+ <a href="subject.html#19098">[ subject ]</a>
+ <a href="author.html#19098">[ 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>