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, "JA Magallón" <<a href="mailto:jamagallon@ono.com">jamagallon@ono.com</a>> wrote:<br>
><br>
> On 06/15/2012 08:54 PM, Anne Wilson wrote:<br>
>><br>
>> On 15/06/12 19:13, Frank Griffin wrote:<br>
>>><br>
>>> On 06/15/2012 01:42 PM, AL13N wrote:<br>
>>>><br>
>>>> Op vrijdag 15 juni 2012 16:46:03 schreef Anne Wilson:<br>
>>>>><br>
>>>>> 'mount: wrong fs type, bad option, bad superblock on<br>
>>>>> 192.168.0.200:/Anne,<br>
>>>>><br>
>>>>> has dmesg something? did you have nfs in lsmod?<br>
>>>>><br>
>>><br>
>>> Shortly before release I and others noticed that a lot of basic services<br>
>>> that were converted to systemd were no longer starting automatically at<br>
>>> boot. I thought that it was fixed, but you might check to see that NFS<br>
>>> has actually been started.<br>
>><br>
>><br>
>> Combining replies:<br>
>><br>
>> Sander: nfs-utils-clients wasn't installed on the misbehaving laptop. After installation, all the 192.168.0.40 mounts work, the 192.168.0.200 ones don't. More digging to be done.<br>
>><br>
>> The errors for those two are:<br>
>><br>
>> 'mount.nfs: rpc.statd is not running but is required for remote locking.<br>
>> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.<br>
>> mount.nfs: an incorrect mount option was specified'<br>
>><br>
>> Not sure what I have to do about statd - my efforts don't seem to have achieved much.<br>
>><br>
>> AL113N: 'useer' is a red herring :-) I was typing what I could see on the netbook screen. This is a new install and I hadn't slowed down the keyboard repeat - doing that now. dmesg didn't have anything to say, and nfs is in lsmod.<br>
>><br>
>> 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've restarted it, but it has no effect on the troublesome mounts.<br>
>><br>
>> Anne<br>
><br>
><br>
> In the failing box, try<br>
><br>
> systemctl start nfs.target<br>
> systemctl start nfs-server.service<br>
Why start server on client side?<br>
><br>
> If after that mounts work, check all your boxes and re-do something like<br>
><br>
> systemctl enable nfs.tartget<br>
> systemctl enable nfs-server.service<br>
><br>
> Problem: after conversion from sysvinit to systemd, nfs is not enabled even<br>
> if it was before. I suppose this will be fixed.<br>
><br>
> And don't worry about nfs-common.service. It is dead and removed, but some<br>
> other services reference it so it appears in listings. I suppose its references<br>
> will be completely removed in next packages... but it doesn't hurt<br>
> (apart your eyes).<br>
For me (on mga2) nfs-common is the service that starts rpc.statd - so i wouldn't call it a dead thing yet, seems to be pretty much needed.</p>
<p>--<br>
Sander<br>
</p>
|