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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-discuss] fstab problem
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20fstab%20problem&In-Reply-To=%3C4FDB84CC.9050800%40kde.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="007891.html">
<LINK REL="Next" HREF="007895.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] fstab problem</H1>
<B>Anne Wilson</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20fstab%20problem&In-Reply-To=%3C4FDB84CC.9050800%40kde.org%3E"
TITLE="[Mageia-discuss] fstab problem">annew at kde.org
</A><BR>
<I>Fri Jun 15 20:54:04 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="007891.html">[Mageia-discuss] fstab problem
</A></li>
<LI>Next message: <A HREF="007895.html">[Mageia-discuss] fstab problem
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7894">[ date ]</a>
<a href="thread.html#7894">[ thread ]</a>
<a href="subject.html#7894">[ subject ]</a>
<a href="author.html#7894">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 15/06/12 19:13, Frank Griffin wrote:
><i> On 06/15/2012 01:42 PM, AL13N wrote:
</I>>><i> Op vrijdag 15 juni 2012 16:46:03 schreef Anne Wilson:
</I>>>><i> 'mount: wrong fs type, bad option, bad superblock on
</I>>>><i> 192.168.0.200:/Anne,
</I>>>><i>
</I>>>><i> has dmesg something? did you have nfs in lsmod?
</I>>>><i>
</I>><i>
</I>><i> Shortly before release I and others noticed that a lot of basic services
</I>><i> that were converted to systemd were no longer starting automatically at
</I>><i> boot. I thought that it was fixed, but you might check to see that NFS
</I>><i> has actually been started.
</I>
Combining replies:
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.
The errors for those two are:
'mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified'
Not sure what I have to do about statd - my efforts don't seem to have
achieved much.
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.
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.
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>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007891.html">[Mageia-discuss] fstab problem
</A></li>
<LI>Next message: <A HREF="007895.html">[Mageia-discuss] fstab problem
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7894">[ date ]</a>
<a href="thread.html#7894">[ thread ]</a>
<a href="subject.html#7894">[ subject ]</a>
<a href="author.html#7894">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
mailing list</a><br>
</body></html>
|
