Hi,
I have setup NFS and I checked every thing with documents and manual.
After the client boots up, it says:
=A0
=A0
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.
mountall: mount /opt [1000] terminated with status 32
=A0
and I can not see the shared folder.
my hosts.allow file contains:
=A0
=A0
portmap: 192.168.1.0/255.255.255.0
lockd: 192.168.1.0/255.255.255.0
rqoutad: 192.168.1.0/255.255.255.0
mountd: 192.168.1.0/255.255.255.0
=A0
=A0
also /etc/exports contain:
/opt=A0=A0=A0=A0=A0=A0=A0 192.168.1.0/255.255.255.0(rw,no_subtree_check=
,sync,no_root_squash)
=A0
=A0
Any idea about that? What does '-o loop' mean?
On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> Hi,
> I have setup NFS and I checked every thing with documents and manual.
> After the client boots up, it says:
> =A0
> =A0
> mount.nfs: rpc.statd is not running but is required for remote lockin=
g.
> mount.nfs: Either use '-o nolock' to keep locks local, or start statd=
=2E
> mountall: mount /opt [1000] terminated with status 32
mount tried to run /usr/sbin/start-statd and it failed for some reason=
=2E
What is in /usr/sbin/start-statd ??
What happens if you run it directly?
What happens if you just run /usr/sbin/rpc.statd??
> =A0
> and I can not see the shared folder.
> my hosts.allow file contains:
> =A0
> =A0
> portmap: 192.168.1.0/255.255.255.0
> lockd: 192.168.1.0/255.255.255.0
> rqoutad: 192.168.1.0/255.255.255.0
> mountd: 192.168.1.0/255.255.255.0
> =A0
> =A0
> also /etc/exports contain:
> /opt=A0=A0=A0=A0=A0=A0=A0 192.168.1.0/255.255.255.0(rw,no_subtree_che=
ck,sync,no_root_squash)
> =A0
> =A0
> Any idea about that? What does '-o loop' mean?
How is that relevant?
man 8 mount
might help you.
NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>mount tried to run=A0 /usr/sbin/start-statd and it failed for some rea=
son.
>What is in /usr/sbin/start-statd ??
>What happens if you run it directly?
>What happens if you just run=A0 /usr/sbin/rpc.statd??
=A0
=A0
root@server:~# find /usr/ -name "start-statd"root@server:~#
I don't have it!!!
=A0
>How is that relevant?
> man 8 mount
>might help you.
=A0
I think the above problem is serious and "-o loop" may not help
// Naderan *Mahmood;
----- Original Message -----
=46rom: NeilBrown <[email protected]>
To: Mahmood Naderan <[email protected]>
Cc: nfs <[email protected]>
Sent: Monday, May 2, 2011 1:05 PM
Subject: Re: rpc.statd is not running but is required
On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> Hi,
> I have setup NFS and I checked every thing with documents and manual.
> After the client boots up, it says:
> =A0
> =A0
> mount.nfs: rpc.statd is not running but is required for remote lockin=
g.
> mount.nfs: Either use '-o nolock' to keep locks local, or start statd=
=2E
> mountall: mount /opt [1000] terminated with status 32
mount tried to run=A0 /usr/sbin/start-statd and it failed for some reas=
on.
What is in /usr/sbin/start-statd ??
What happens if you run it directly?
What happens if you just run=A0 /usr/sbin/rpc.statd??
> =A0
> and I can not see the shared folder.
> my hosts.allow file contains:
> =A0
> =A0
> portmap: 192.168.1.0/255.255.255.0
> lockd: 192.168.1.0/255.255.255.0
> rqoutad: 192.168.1.0/255.255.255.0
> mountd: 192.168.1.0/255.255.255.0
> =A0
> =A0
> also /etc/exports contain:
> /opt=A0=A0=A0=A0=A0=A0=A0 192.168.1.0/255.255.255.0(rw,no_subtree_che=
ck,sync,no_root_squash)
> =A0
> =A0
> Any idea about that? What does '-o loop' mean?
How is that relevant?
man 8 mount
might help you.
NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at=A0 http://vger.kernel.org/majordomo-info.html
I heve this service
=A0
mahmood@server:~$ sudo=A0 /etc/init.d/nfs-kernel-server restart
=A0* Stopping NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
=A0* Unexporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
=A0* Exporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK=
]
=A0* Starting NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
=A0
I use debian based linux. Is that what you meant?
// Naderan *Mahmood;
----- Original Message -----
=46rom: Dennis Jacobfeuerborn <[email protected]>
To: NeilBrown <[email protected]>
Cc: Mahmood Naderan <[email protected]>; nfs <[email protected]=
org>
Sent: Monday, May 2, 2011 2:30 PM
Subject: Re: rpc.statd is not running but is required
On 05/02/2011 10:35 AM, NeilBrown wrote:
> On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> <[email protected]>=A0 wrote:
>
>> Hi,
>> I have setup NFS and I checked every thing with documents and manual=
=2E
>> After the client boots up, it says:
>>
>>
>> mount.nfs: rpc.statd is not running but is required for remote locki=
ng.
>> mount.nfs: Either use '-o nolock' to keep locks local, or start stat=
d.
>> mountall: mount /opt [1000] terminated with status 32
>
> mount tried to run=A0 /usr/sbin/start-statd and it failed for some re=
ason.
> What is in /usr/sbin/start-statd ??
> What happens if you run it directly?
> What happens if you just run=A0 /usr/sbin/rpc.statd??
>
Have you tried checking if the /etc/init.d/nfslock service is enabled a=
nd=20
running?
Regards,
=A0 Dennis
On 05/02/2011 10:35 AM, NeilBrown wrote:
> On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> <[email protected]> wrote:
>
>> Hi,
>> I have setup NFS and I checked every thing with documents and manual.
>> After the client boots up, it says:
>>
>>
>> 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.
>> mountall: mount /opt [1000] terminated with status 32
>
> mount tried to run /usr/sbin/start-statd and it failed for some reason.
> What is in /usr/sbin/start-statd ??
> What happens if you run it directly?
> What happens if you just run /usr/sbin/rpc.statd??
>
Have you tried checking if the /etc/init.d/nfslock service is enabled and
running?
Regards,
Dennis
On Mon, 2 May 2011 03:03:28 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> I heve this service
> =A0
> mahmood@server:~$ sudo=A0 /etc/init.d/nfs-kernel-server restart
> =A0* Stopping NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Unexporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Exporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=
OK ]
> =A0* Starting NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
>=20
> =A0
> I use debian based linux. Is that what you meant?
>=20
> // Naderan *Mahmood;
>=20
>=20
> ----- Original Message -----
> From: Dennis Jacobfeuerborn <[email protected]>
> To: NeilBrown <[email protected]>
> Cc: Mahmood Naderan <[email protected]>; nfs <[email protected]=
l.org>
> Sent: Monday, May 2, 2011 2:30 PM
> Subject: Re: rpc.statd is not running but is required
>=20
> On 05/02/2011 10:35 AM, NeilBrown wrote:
> > On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> > <[email protected]>=A0 wrote:
> >
> >> Hi,
> >> I have setup NFS and I checked every thing with documents and manu=
al.
> >> After the client boots up, it says:
> >>
> >>
> >> mount.nfs: rpc.statd is not running but is required for remote loc=
king.
> >> mount.nfs: Either use '-o nolock' to keep locks local, or start st=
atd.
> >> mountall: mount /opt [1000] terminated with status 32
> >
> > mount tried to run=A0 /usr/sbin/start-statd and it failed for some =
reason.
> > What is in /usr/sbin/start-statd ??
> > What happens if you run it directly?
> > What happens if you just run=A0 /usr/sbin/rpc.statd??
> >
>=20
> Have you tried checking if the /etc/init.d/nfslock service is enabled=
and=20
> running?
>=20
> Regards,
> =A0 Dennis
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2 May 2011 03:03:28 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> I heve this service
> =A0
> mahmood@server:~$ sudo=A0 /etc/init.d/nfs-kernel-server restart
> =A0* Stopping NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Unexporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Exporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=
OK ]
> =A0* Starting NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
>=20
> =A0
> I use debian based linux. Is that what you meant?
(sorry - clicked wrong button before.
Yes, it seems Debian doesn't supply start-statd. I wonder why.
They rely on
/etc/init.d/nfs-common start
to start statd. That should work unless NEED_STATD is set to 'no' in=20
/etc/default/nfs-common.
What is in /etc/default/nfs-common??
If you=20
/etc/init.d/nfs-common restart
does that start statd?
NeilBrown
>=20
> // Naderan *Mahmood;
>=20
>=20
> ----- Original Message -----
> From: Dennis Jacobfeuerborn <[email protected]>
> To: NeilBrown <[email protected]>
> Cc: Mahmood Naderan <[email protected]>; nfs <[email protected]=
l.org>
> Sent: Monday, May 2, 2011 2:30 PM
> Subject: Re: rpc.statd is not running but is required
>=20
> On 05/02/2011 10:35 AM, NeilBrown wrote:
> > On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> > <[email protected]>=A0 wrote:
> >
> >> Hi,
> >> I have setup NFS and I checked every thing with documents and manu=
al.
> >> After the client boots up, it says:
> >>
> >>
> >> mount.nfs: rpc.statd is not running but is required for remote loc=
king.
> >> mount.nfs: Either use '-o nolock' to keep locks local, or start st=
atd.
> >> mountall: mount /opt [1000] terminated with status 32
> >
> > mount tried to run=A0 /usr/sbin/start-statd and it failed for some =
reason.
> > What is in /usr/sbin/start-statd ??
> > What happens if you run it directly?
> > What happens if you just run=A0 /usr/sbin/rpc.statd??
> >
>=20
> Have you tried checking if the /etc/init.d/nfslock service is enabled=
and=20
> running?
>=20
> Regards,
> =A0 Dennis
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>to start statd. That should work unless NEED_STATD is set to 'no' in=20
>/etc/default/nfs-common.
mahmood@server:~$ cat /etc/default/nfs-common
# If you do not set values for the NEED_ options, they will be attempte=
d
# autodetected; this should be sufficient for most people. Valid altern=
atives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=3D
# Options for rpc.statd.
#=A0=A0 Should rpc.statd listen on a specific port? This is especially =
useful
#=A0=A0 when you have a port-based firewall. To use a fixed port, set t=
his
#=A0=A0 this variable to a statd argument like: "--port 4000 --outgoing=
-port 4001".
#=A0=A0 For more information, see rpc.statd(8) or http://wiki.debian.or=
g/?SecuringNFS
STATDOPTS=3D
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=3D
# Do you want to start the gssd daemon? It is required for Kerberos mou=
nts.
NEED_GSSD=3D
Should I NEED_STATD to yes?
>What is in /etc/default/nfs-common??
>If you=20
>/etc/init.d/nfs-common restart
>does that start statd?
As I said, I have only nfs-kernel-server
mahmood@server:~$ ls /etc/init.d/nfs*
/etc/init.d/nfs-kernel-server
One more question? Can I install statd?
mahmood@server:~$ sudo apt-get install stat
stat statcvs statd statgrab statnews statserial =
statsvn
So you recommend that?
// Naderan *Mahmood;
----- Original Message -----
=46rom: NeilBrown <[email protected]>
To: Mahmood Naderan <[email protected]>
Cc: Dennis Jacobfeuerborn <[email protected]>; nfs <linux-nfs@vger.=
kernel.org>
Sent: Monday, May 2, 2011 3:12 PM
Subject: Re: rpc.statd is not running but is required
On Mon, 2 May 2011 03:03:28 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> I heve this service
> =A0
> mahmood@server:~$ sudo=A0 /etc/init.d/nfs-kernel-server restart
> =A0* Stopping NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Unexporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Exporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=
OK ]
> =A0* Starting NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
>=20
> =A0
> I use debian based linux. Is that what you meant?
(sorry - clicked wrong button before.
Yes, it seems Debian doesn't supply start-statd.=A0 I wonder why.
They rely on
=A0 =A0 /etc/init.d/nfs-common start
to start statd.=A0 That should work unless NEED_STATD is set to 'no' in=
=20
/etc/default/nfs-common.
What is in /etc/default/nfs-common??
If you=20
=A0 /etc/init.d/nfs-common restart
does that start statd?
NeilBrown
>=20
> // Naderan *Mahmood;
>=20
>=20
> ----- Original Message -----
> From: Dennis Jacobfeuerborn <[email protected]>
> To: NeilBrown <[email protected]>
> Cc: Mahmood Naderan <[email protected]>; nfs <[email protected]=
l.org>
> Sent: Monday, May 2, 2011 2:30 PM
> Subject: Re: rpc.statd is not running but is required
>=20
> On 05/02/2011 10:35 AM, NeilBrown wrote:
> > On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> > <[email protected]>=A0 wrote:
> >
> >> Hi,
> >> I have setup NFS and I checked every thing with documents and manu=
al.
> >> After the client boots up, it says:
> >>
> >>
> >> mount.nfs: rpc.statd is not running but is required for remote loc=
king.
> >> mount.nfs: Either use '-o nolock' to keep locks local, or start st=
atd.
> >> mountall: mount /opt [1000] terminated with status 32
> >
> > mount tried to run=A0 /usr/sbin/start-statd and it failed for some =
reason.
> > What is in /usr/sbin/start-statd ??
> > What happens if you run it directly?
> > What happens if you just run=A0 /usr/sbin/rpc.statd??
> >
>=20
> Have you tried checking if the /etc/init.d/nfslock service is enabled=
and=20
> running?
>=20
> Regards,
> =A0=A0 Dennis
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at=A0 http://vger.kernel.org/majordomo-info.html
I have to say somethig that might related to this problem. Earleir I ha=
d problem with these files:
/etc/passwd
/etc/group
/etc/shadow
=A0
Hopefully I had backed up them to *.bak. The procedure to fix those fil=
e names was booting a live cd and then:
cp /etc/passwd.bak /etc/passwd
cp /etc/group.bak /etc/group
cp /etc/shadow.bak /etc/shadow
=A0
I said that becuase I found that statd has a user name which I didn't t=
hink about it.
here they are:
mahmood@server:~$ cat /etc/passwd | grep "statd"
statd:x:108:65534::/var/lib/nfs:/bin/false
mahmood@server:~$ cat /etc/group | grep "statd"
mahmood@server:~$ sudo cat /etc/shadow | grep "statd"
statd:*:14970:0:99999:7:::
Are they normal?=A0
// Naderan *Mahmood;
----- Original Message -----
=46rom: NeilBrown <[email protected]>
To: Mahmood Naderan <[email protected]>
Cc: Dennis Jacobfeuerborn <[email protected]>; nfs <linux-nfs@vger.=
kernel.org>
Sent: Monday, May 2, 2011 3:12 PM
Subject: Re: rpc.statd is not running but is required
On Mon, 2 May 2011 03:03:28 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> I heve this service
> =A0
> mahmood@server:~$ sudo=A0 /etc/init.d/nfs-kernel-server restart
> =A0* Stopping NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Unexporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Exporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=
OK ]
> =A0* Starting NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
>=20
> =A0
> I use debian based linux. Is that what you meant?
(sorry - clicked wrong button before.
Yes, it seems Debian doesn't supply start-statd.=A0 I wonder why.
They rely on
=A0 =A0 /etc/init.d/nfs-common start
to start statd.=A0 That should work unless NEED_STATD is set to 'no' in=
=20
/etc/default/nfs-common.
What is in /etc/default/nfs-common??
If you=20
=A0 /etc/init.d/nfs-common restart
does that start statd?
NeilBrown
>=20
> // Naderan *Mahmood;
>=20
>=20
> ----- Original Message -----
> From: Dennis Jacobfeuerborn <[email protected]>
> To: NeilBrown <[email protected]>
> Cc: Mahmood Naderan <[email protected]>; nfs <[email protected]=
l.org>
> Sent: Monday, May 2, 2011 2:30 PM
> Subject: Re: rpc.statd is not running but is required
>=20
> On 05/02/2011 10:35 AM, NeilBrown wrote:
> > On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> > <[email protected]>=A0 wrote:
> >
> >> Hi,
> >> I have setup NFS and I checked every thing with documents and manu=
al.
> >> After the client boots up, it says:
> >>
> >>
> >> mount.nfs: rpc.statd is not running but is required for remote loc=
king.
> >> mount.nfs: Either use '-o nolock' to keep locks local, or start st=
atd.
> >> mountall: mount /opt [1000] terminated with status 32
> >
> > mount tried to run=A0 /usr/sbin/start-statd and it failed for some =
reason.
> > What is in /usr/sbin/start-statd ??
> > What happens if you run it directly?
> > What happens if you just run=A0 /usr/sbin/rpc.statd??
> >
>=20
> Have you tried checking if the /etc/init.d/nfslock service is enabled=
and=20
> running?
>=20
> Regards,
> =A0=A0 Dennis
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at=A0 http://vger.kernel.org/majordomo-info.html
Sorry but I found another thing that may point to problem
In the server log I see=20
mountd[5744]: authenticated mount request from 192.168.1.3:866 for /hom=
e/nfsroot (/home/nfsroot)
192.168.1.3 is the client and /home/nfsroot is the place that clients b=
oots from there (an image is installed so the client boots from there)
Does that mean the permission is denied for client? How can I fix that?
Appreciate your help and comments.
// Naderan *Mahmood;
----- Original Message -----
=46rom: NeilBrown <[email protected]>
To: Mahmood Naderan <[email protected]>
Cc: Dennis Jacobfeuerborn <[email protected]>; nfs <linux-nfs@vger.=
kernel.org>
Sent: Monday, May 2, 2011 3:12 PM
Subject: Re: rpc.statd is not running but is required
On Mon, 2 May 2011 03:03:28 -0700 (PDT) Mahmood Naderan
<[email protected]> wrote:
> I heve this service
> =A0
> mahmood@server:~$ sudo=A0 /etc/init.d/nfs-kernel-server restart
> =A0* Stopping NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Unexporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
> =A0* Exporting directories for NFS kernel daemon...=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [=
OK ]
> =A0* Starting NFS kernel daemon=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 [ OK ]
>=20
> =A0
> I use debian based linux. Is that what you meant?
(sorry - clicked wrong button before.
Yes, it seems Debian doesn't supply start-statd.=A0 I wonder why.
They rely on
=A0 =A0 /etc/init.d/nfs-common start
to start statd.=A0 That should work unless NEED_STATD is set to 'no' in=
=20
/etc/default/nfs-common.
What is in /etc/default/nfs-common??
If you=20
=A0 /etc/init.d/nfs-common restart
does that start statd?
NeilBrown
>=20
> // Naderan *Mahmood;
>=20
>=20
> ----- Original Message -----
> From: Dennis Jacobfeuerborn <[email protected]>
> To: NeilBrown <[email protected]>
> Cc: Mahmood Naderan <[email protected]>; nfs <[email protected]=
l.org>
> Sent: Monday, May 2, 2011 2:30 PM
> Subject: Re: rpc.statd is not running but is required
>=20
> On 05/02/2011 10:35 AM, NeilBrown wrote:
> > On Mon, 2 May 2011 00:59:01 -0700 (PDT) Mahmood Naderan
> > <[email protected]>=A0 wrote:
> >
> >> Hi,
> >> I have setup NFS and I checked every thing with documents and manu=
al.
> >> After the client boots up, it says:
> >>
> >>
> >> mount.nfs: rpc.statd is not running but is required for remote loc=
king.
> >> mount.nfs: Either use '-o nolock' to keep locks local, or start st=
atd.
> >> mountall: mount /opt [1000] terminated with status 32
> >
> > mount tried to run=A0 /usr/sbin/start-statd and it failed for some =
reason.
> > What is in /usr/sbin/start-statd ??
> > What happens if you run it directly?
> > What happens if you just run=A0 /usr/sbin/rpc.statd??
> >
>=20
> Have you tried checking if the /etc/init.d/nfslock service is enabled=
and=20
> running?
>=20
> Regards,
> =A0=A0 Dennis
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to [email protected]
> More majordomo info at=A0 http://vger.kernel.org/majordomo-info.html
FIX: rpc.statd is not running but is required for remote locking.
For future reference, you need to have rpcbind daemon running on LOCAL MACHINE
where you want to mount the nfs share as well.
FIX: rpc.statd is not running but is required for remote locking.
For future reference, you need to have rpcbind daemon running on LOCAL MACHINE
where you want to mount the nfs share as well.