Discussion:
clients cannot reconnect to mounted nfs shares after server restart
camden lindsay
2011-02-01 03:24:30 UTC
Permalink
Having an issue i believe is an NFS bug, but would like someone to
verify as well as... point me the correct direction to submit a bug as
needed if it indeed is.
Situation:
NFS server running
Client connected with mounted share
NFS server is shut down -- (halt or /etc/init.d/nfs stop)
NFS server is turned on (booted or /etc/init.d/nfs start)

Outcome:
NFS client that was connected does not reconnect to that share automati=
cally
NFS client that was connected cannot reconnect via umount then mount ag=
ain
No other nfs client can connect to that share, before or after origial
NFS clients attempts to connect/reconnect
NFS clients CAN connect to a different share.
Details/logs:
Server shows that client is authenticating:
=46eb =A01 03:01:47 BigBox mountd[6557]: authenticated mount request fr=
om
192.168.11.49:674 for /mnt/store/public (/mnt/store/public)
=46eb =A01 03:01:48 BigBox mountd[6557]: authenticated mount request fr=
om
192.168.11.49:763 for /mnt/store/public (/mnt/store/public)
=46eb =A01 03:01:50 BigBox mountd[6557]: authenticated mount request fr=
om
192.168.11.49:932 for /mnt/store/public (/mnt/store/public)
=46eb =A01 03:01:54 BigBox mountd[6557]: authenticated mount request fr=
om
192.168.11.49:942 for /mnt/store/public (/mnt/store/public)

Client shows retransmission:
***@shobuntu:~$ sudo mount -v -t nfs bigbox:/mnt/store/public Public/
mount.nfs: timeout set for Mon Jan 31 19:09:32 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'

Server Version:
net-fs/nfs-utils
=A0=A0 =A0 =A0Latest version available: 1.1.4-r1
=A0=A0 =A0 =A0Latest version installed: 1.1.4-r1
=A0=A0 =A0 =A0Size of files: 574 kB
=A0=A0 =A0 =A0Homepage: =A0 =A0 =A0http://linux-nfs.org/
=A0=A0 =A0 =A0Description: =A0 NFS client and server daemons
=A0=A0 =A0 =A0License: =A0 =A0 =A0 GPL-2
(server is on Gentoo, client on Ubuntu)
Thanks!
Camden
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
J. Bruce Fields
2011-02-01 18:15:10 UTC
Permalink
Post by camden lindsay
Having an issue i believe is an NFS bug, but would like someone to
verify as well as... point me the correct direction to submit a bug a=
s
Post by camden lindsay
needed if it indeed is.
NFS server running
Client connected with mounted share
NFS server is shut down -- (halt or /etc/init.d/nfs stop)
NFS server is turned on (booted or /etc/init.d/nfs start)
=20
NFS client that was connected does not reconnect to that share automa=
tically
Post by camden lindsay
NFS client that was connected cannot reconnect via umount then mount =
again
Post by camden lindsay
No other nfs client can connect to that share, before or after origia=
l

How long have you waited?
Post by camden lindsay
NFS clients attempts to connect/reconnect
NFS clients CAN connect to a different share.
Feb =C2=A01 03:01:47 BigBox mountd[6557]: authenticated mount request=
from
Post by camden lindsay
192.168.11.49:674 for /mnt/store/public (/mnt/store/public)
Feb =C2=A01 03:01:48 BigBox mountd[6557]: authenticated mount request=
from
Post by camden lindsay
192.168.11.49:763 for /mnt/store/public (/mnt/store/public)
Feb =C2=A01 03:01:50 BigBox mountd[6557]: authenticated mount request=
from
Post by camden lindsay
192.168.11.49:932 for /mnt/store/public (/mnt/store/public)
Feb =C2=A01 03:01:54 BigBox mountd[6557]: authenticated mount request=
from
Post by camden lindsay
192.168.11.49:942 for /mnt/store/public (/mnt/store/public)
A network trace (tcpdump -s0 -wtmp.pcap, then reproduce the problem,
then ^C tcpdump, then send us tmp.pcap) might help.
Post by camden lindsay
=20
c/
Post by camden lindsay
mount.nfs: timeout set for Mon Jan 31 19:09:32 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
=20
net-fs/nfs-utils
=C2=A0=C2=A0 =C2=A0 =C2=A0Latest version available: 1.1.4-r1
=C2=A0=C2=A0 =C2=A0 =C2=A0Latest version installed: 1.1.4-r1
=C2=A0=C2=A0 =C2=A0 =C2=A0Size of files: 574 kB
=C2=A0=C2=A0 =C2=A0 =C2=A0Homepage: =C2=A0 =C2=A0 =C2=A0http://linux-=
nfs.org/
Post by camden lindsay
=C2=A0=C2=A0 =C2=A0 =C2=A0Description: =C2=A0 NFS client and server d=
aemons
Post by camden lindsay
=C2=A0=C2=A0 =C2=A0 =C2=A0License: =C2=A0 =C2=A0 =C2=A0 GPL-2
(server is on Gentoo, client on Ubuntu)
Note most of the NFS code is actually in the kernel, so the kernel
version(s) involved would be useful too.

--b.
Post by camden lindsay
Thanks!
Camden
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
Post by camden lindsay
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
camden lindsay
2011-02-04 09:31:05 UTC
Permalink
Thanks for the response:
I have waited quite some time-- many minutes-- and still cannot reconne=
ct.

Server --> BigBox dylan # uname -a
Linux BigBox 2.6.36-gentoo-r5 #5 SMP Tue Feb 1 06:57:03 PST 2011
x86_64 Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz GenuineIntel GNU/Linux

What i have found is that, with a newer client, i get slightly more
information at the command line, pointing to stale nfs filehandle:
Client1:
Linux shobuntu 2.6.24-28-generic #1 SMP Wed Nov 24 09:30:14 UTC 2010
i686 GNU/Linux
mount.nfs: timeout set for Fri Feb 4 01:19:37 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'

Client2:
Linux core2buntu 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 23:42:43
UTC 2011 x86_64 GNU/Linux
mount.nfs: timeout set for Fri Feb 4 01:18:17 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: mount(2): Stale NFS file handle
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: mount(2): Stale NFS file handle
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: mount(2): Stale NFS file handle


Should this automatically converge at some point?
If so, how long should i expect for convergence?

Thanks!
Camden
Post by J. Bruce Fields
Post by camden lindsay
Having an issue i believe is an NFS bug, but would like someone to
verify as well as... point me the correct direction to submit a bug=
as
Post by J. Bruce Fields
Post by camden lindsay
needed if it indeed is.
NFS server running
Client connected with mounted share
NFS server is shut down -- (halt or /etc/init.d/nfs stop)
NFS server is turned on (booted or /etc/init.d/nfs start)
NFS client that was connected does not reconnect to that share auto=
matically
Post by J. Bruce Fields
Post by camden lindsay
NFS client that was connected cannot reconnect via umount then moun=
t again
Post by J. Bruce Fields
Post by camden lindsay
No other nfs client can connect to that share, before or after orig=
ial
Post by J. Bruce Fields
How long have you waited?
Post by camden lindsay
NFS clients attempts to connect/reconnect
NFS clients CAN connect to a different share.
Feb =A01 03:01:47 BigBox mountd[6557]: authenticated mount request =
from
Post by J. Bruce Fields
Post by camden lindsay
192.168.11.49:674 for /mnt/store/public (/mnt/store/public)
Feb =A01 03:01:48 BigBox mountd[6557]: authenticated mount request =
from
Post by J. Bruce Fields
Post by camden lindsay
192.168.11.49:763 for /mnt/store/public (/mnt/store/public)
Feb =A01 03:01:50 BigBox mountd[6557]: authenticated mount request =
from
Post by J. Bruce Fields
Post by camden lindsay
192.168.11.49:932 for /mnt/store/public (/mnt/store/public)
Feb =A01 03:01:54 BigBox mountd[6557]: authenticated mount request =
from
Post by J. Bruce Fields
Post by camden lindsay
192.168.11.49:942 for /mnt/store/public (/mnt/store/public)
A network trace (tcpdump -s0 -wtmp.pcap, then reproduce the problem,
then ^C tcpdump, then send us tmp.pcap) might help.
lic/
Post by J. Bruce Fields
Post by camden lindsay
mount.nfs: timeout set for Mon Jan 31 19:09:32 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
net-fs/nfs-utils
=A0=A0 =A0 =A0Latest version available: 1.1.4-r1
=A0=A0 =A0 =A0Latest version installed: 1.1.4-r1
=A0=A0 =A0 =A0Size of files: 574 kB
=A0=A0 =A0 =A0Homepage: =A0 =A0 =A0http://linux-nfs.org/
=A0=A0 =A0 =A0Description: =A0 NFS client and server daemons
=A0=A0 =A0 =A0License: =A0 =A0 =A0 GPL-2
(server is on Gentoo, client on Ubuntu)
Note most of the NFS code is actually in the kernel, so the kernel
version(s) involved would be useful too.
--b.
Post by camden lindsay
Thanks!
Camden
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs=
" in
Post by J. Bruce Fields
Post by camden lindsay
More majordomo info at =A0http://vger.kernel.org/majordomo-info.htm=
l
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
J. Bruce Fields
2011-02-06 20:47:20 UTC
Permalink
I have waited quite some time-- many minutes-- and still cannot recon=
nect.

The wait shouldn't be more than a minute or two after the nfs server is
back up and running. And mount should pretty much never see a stale
filehandle error.

A network trace showing the stale errors after reboot, together with th=
e
output of

cat /proc/net/rpc/nfsd.*/content
blkid

on the server, could be useful.

--b.
=20
Server --> BigBox dylan # uname -a
Linux BigBox 2.6.36-gentoo-r5 #5 SMP Tue Feb 1 06:57:03 PST 2011
=20
What i have found is that, with a newer client, i get slightly more
Linux shobuntu 2.6.24-28-generic #1 SMP Wed Nov 24 09:30:14 UTC 2010
i686 GNU/Linux
mount.nfs: timeout set for Fri Feb 4 01:19:37 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
=20
Linux core2buntu 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 23:42:43
UTC 2011 x86_64 GNU/Linux
mount.nfs: timeout set for Fri Feb 4 01:18:17 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: mount(2): Stale NFS file handle
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: mount(2): Stale NFS file handle
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: mount(2): Stale NFS file handle
=20
=20
Should this automatically converge at some point?
If so, how long should i expect for convergence?
=20
Thanks!
Camden
=20
Post by J. Bruce Fields
Having an issue i believe is an NFS bug, but would like someone t=
o
Post by J. Bruce Fields
verify as well as... point me the correct direction to submit a b=
ug as
Post by J. Bruce Fields
needed if it indeed is.
NFS server running
Client connected with mounted share
NFS server is shut down -- (halt or /etc/init.d/nfs stop)
NFS server is turned on (booted or /etc/init.d/nfs start)
NFS client that was connected does not reconnect to that share au=
tomatically
Post by J. Bruce Fields
NFS client that was connected cannot reconnect via umount then mo=
unt again
Post by J. Bruce Fields
No other nfs client can connect to that share, before or after or=
igial
Post by J. Bruce Fields
How long have you waited?
NFS clients attempts to connect/reconnect
NFS clients CAN connect to a different share.
Feb =C2=A01 03:01:47 BigBox mountd[6557]: authenticated mount req=
uest from
Post by J. Bruce Fields
192.168.11.49:674 for /mnt/store/public (/mnt/store/public)
Feb =C2=A01 03:01:48 BigBox mountd[6557]: authenticated mount req=
uest from
Post by J. Bruce Fields
192.168.11.49:763 for /mnt/store/public (/mnt/store/public)
Feb =C2=A01 03:01:50 BigBox mountd[6557]: authenticated mount req=
uest from
Post by J. Bruce Fields
192.168.11.49:932 for /mnt/store/public (/mnt/store/public)
Feb =C2=A01 03:01:54 BigBox mountd[6557]: authenticated mount req=
uest from
Post by J. Bruce Fields
192.168.11.49:942 for /mnt/store/public (/mnt/store/public)
A network trace (tcpdump -s0 -wtmp.pcap, then reproduce the problem=
,
Post by J. Bruce Fields
then ^C tcpdump, then send us tmp.pcap) might help.
ublic/
Post by J. Bruce Fields
mount.nfs: timeout set for Mon Jan 31 19:09:32 2011
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
mount.nfs: text-based options: 'addr=3D192.168.11.10'
net-fs/nfs-utils
=C2=A0=C2=A0 =C2=A0 =C2=A0Latest version available: 1.1.4-r1
=C2=A0=C2=A0 =C2=A0 =C2=A0Latest version installed: 1.1.4-r1
=C2=A0=C2=A0 =C2=A0 =C2=A0Size of files: 574 kB
=C2=A0=C2=A0 =C2=A0 =C2=A0Homepage: =C2=A0 =C2=A0 =C2=A0http://li=
nux-nfs.org/
Post by J. Bruce Fields
=C2=A0=C2=A0 =C2=A0 =C2=A0Description: =C2=A0 NFS client and serv=
er daemons
Post by J. Bruce Fields
=C2=A0=C2=A0 =C2=A0 =C2=A0License: =C2=A0 =C2=A0 =C2=A0 GPL-2
(server is on Gentoo, client on Ubuntu)
Note most of the NFS code is actually in the kernel, so the kernel
version(s) involved would be useful too.
--b.
Thanks!
Camden
--
To unsubscribe from this list: send the line "unsubscribe linux-n=
fs" in
Post by J. Bruce Fields
More majordomo info at =C2=A0http://vger.kernel.org/majordomo-inf=
o.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Continue reading on narkive:
Search results for 'clients cannot reconnect to mounted nfs shares after server restart' (Questions and Answers)
14
replies
Creating a "Why we should switch to Mac" Speech. Help Please?
started 2007-10-26 15:44:14 UTC
desktops
Loading...