1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
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 écrit :
><i> -----BEGIN PGP SIGNED MESSAGE-----
</I>><i> Hash: SHA1
</I>><i>
</I>><i> On Monday 01 Oct 2012 13:18:36 Guillaume Rousse wrote:
</I>>><i> Le 22/09/2012 21:16, Anne Wilson a écrit :
</I>>>><i> udp 0 0 *:nfs *:*
</I>>>><i>
</I>>>><i> unfsd
</I>>><i>
</I>>><i> Ouch... You're running an obsolete alternative nfs server. You
</I>>><i> should uninstall the unfs3 package, and this package should get
</I>>><i> removed
</I>><i> from
</I>>><i> the distribution.
</I>>><i>
</I>>><i> To summarize, here are the mandatory steps: - check you have
</I>>><i> nfs-utils-clients installed on clients - check you have
</I>>><i> nfs-utils-clients and nfs-utils installed on server - check
</I>>><i> rpcbind, and nfs-common services are running on clients - check
</I>>><i> rpcbind, nfs-common and nfs-server services are running on
</I>><i> the
</I>>><i> server
</I>>><i>
</I>><i> Not sure of the command-line for checking things that don't respond to
</I>><i> "service whatever status", but MCC says all those services are running
</I>><i> on the server.
</I>MCC won't give any useful detail, "service nfs-common status" will...
[..]
>><i> Now, to ensure usage of NFSv4 instead of obsolete NFSv3: - check
</I>>><i> every host is configured to run rpc.idmapd, meaning NEED_IDMAPD=yes
</I>>><i> in /etc/sysconfig/nfs-common
</I>><i>
</I>><i> Done
</I>><i>
</I>>><i> - check your server export a root filesystem, using fsid=0 options
</I>>><i> in its /etc/exports configuration file
</I>><i>
</I>><i> Added that - how do I tell it to ignore the old exports and act on
</I>><i> those in /etc/exports? I can't find my notes about that.
</I>Quick answer: service nfs-server restart
>><i> - drop all your legacy nfs options, such as wsize and rsize from
</I>>><i> your mount options
</I>>><i>
</I>><i> Done - the lines now match the working QNAS mounts, eg
</I>><i>
</I>><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.
>><i> Last, you'd better use autofs to mount those filesystems on
</I>>><i> demand, rather than hardcoding them in /etc/fstab, which avoid to
</I>>><i> relies on server availability during the boot.
</I>><i>
</I>><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>
|
