summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/attachments/20120616/2d57c60d/attachment.html
blob: fbe12ce7f1f1074730c79df5e9bcd3d7a200c059 (plain)
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
<p>On Jun 16, 2012 1:36 AM, &quot;JA Magallón&quot; &lt;<a href="mailto:jamagallon@ono.com">jamagallon@ono.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 06/15/2012 08:54 PM, Anne Wilson wrote:<br>
&gt;&gt;<br>
&gt;&gt; On 15/06/12 19:13, Frank Griffin wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On 06/15/2012 01:42 PM, AL13N wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Op vrijdag 15 juni 2012 16:46:03 schreef Anne Wilson:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &#39;mount: wrong fs type, bad option, bad superblock on<br>
&gt;&gt;&gt;&gt;&gt; 192.168.0.200:/Anne,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; has dmesg something? did you have nfs in lsmod?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Shortly before release I and others noticed that a lot of basic services<br>
&gt;&gt;&gt; that were converted to systemd were no longer starting automatically at<br>
&gt;&gt;&gt; boot. I thought that it was fixed, but you might check to see that NFS<br>
&gt;&gt;&gt; has actually been started.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Combining replies:<br>
&gt;&gt;<br>
&gt;&gt; Sander:  nfs-utils-clients wasn&#39;t installed on the misbehaving laptop. After installation, all the 192.168.0.40 mounts work, the 192.168.0.200 ones don&#39;t.  More digging to be done.<br>
&gt;&gt;<br>
&gt;&gt; The errors for those two are:<br>
&gt;&gt;<br>
&gt;&gt; &#39;mount.nfs: rpc.statd is not running but is required for remote locking.<br>
&gt;&gt; mount.nfs: Either use &#39;-o nolock&#39; to keep locks local, or start statd.<br>
&gt;&gt; mount.nfs: an incorrect mount option was specified&#39;<br>
&gt;&gt;<br>
&gt;&gt; Not sure what I have to do about statd - my efforts don&#39;t seem to have achieved much.<br>
&gt;&gt;<br>
&gt;&gt; AL113N: &#39;useer&#39; is a red herring :-)  I was typing what I could see on the netbook screen.  This is a new install and I hadn&#39;t slowed down the keyboard repeat - doing that now.  dmesg didn&#39;t have anything to say, and nfs is in lsmod.<br>

&gt;&gt;<br>
&gt;&gt; Frank: since the 192.168.0.40 mounts are now working, I think we can assume that nfs is started.  Or maybe not - nfs-common.service is reported as loaded but dead.  I&#39;ve restarted it, but it has no effect on the troublesome mounts.<br>

&gt;&gt;<br>
&gt;&gt; Anne<br>
&gt;<br>
&gt;<br>
&gt; In the failing box, try<br>
&gt;<br>
&gt; systemctl start nfs.target<br>
&gt; systemctl start nfs-server.service<br>
Why start server on client side?<br>
&gt;<br>
&gt; If after that mounts work, check all your boxes and re-do something like<br>
&gt;<br>
&gt; systemctl enable nfs.tartget<br>
&gt; systemctl enable nfs-server.service<br>
&gt;<br>
&gt; Problem: after conversion from sysvinit to systemd, nfs is not enabled even<br>
&gt; if it was before. I suppose this will be fixed.<br>
&gt;<br>
&gt; And don&#39;t worry about nfs-common.service. It is dead and removed, but some<br>
&gt; other services reference it so it appears in listings. I suppose its references<br>
&gt; will be completely removed in next packages... but it doesn&#39;t hurt<br>
&gt; (apart your eyes).<br>
For me (on mga2) nfs-common is the service that starts rpc.statd - so i wouldn&#39;t call it a dead thing yet, seems to be pretty much needed.</p>
<p>--<br>
Sander<br>
</p>