From: "J. Bruce Fields" <bfields@fieldses.org>
To: camden lindsay <camden.lindsay@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: clients cannot reconnect to mounted nfs shares after server restart
Date: Tue, 1 Feb 2011 13:15:10 -0500 [thread overview]
Message-ID: <20110201181510.GA25136@fieldses.org> (raw)
In-Reply-To: <AANLkTimA-sCz8LQLu1weh-qQOm30jHYyO3qtxmPDPX98@mail.gmail.com>
On Mon, Jan 31, 2011 at 07:24:30PM -0800, camden lindsay wrote:
> 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 automatically
> NFS client that was connected cannot reconnect via umount then mount again
> No other nfs client can connect to that share, before or after origial
How long have you waited?
> NFS clients attempts to connect/reconnect
> NFS clients CAN connect to a different share.
> Details/logs:
> Server shows that client is authenticating:
> Feb 1 03:01:47 BigBox mountd[6557]: authenticated mount request from
> 192.168.11.49:674 for /mnt/store/public (/mnt/store/public)
> Feb 1 03:01:48 BigBox mountd[6557]: authenticated mount request from
> 192.168.11.49:763 for /mnt/store/public (/mnt/store/public)
> Feb 1 03:01:50 BigBox mountd[6557]: authenticated mount request from
> 192.168.11.49:932 for /mnt/store/public (/mnt/store/public)
> Feb 1 03:01:54 BigBox mountd[6557]: authenticated mount request from
> 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.
>
> Client shows retransmission:
> dylan@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=192.168.11.10'
> mount.nfs: text-based options: 'addr=192.168.11.10'
> mount.nfs: text-based options: 'addr=192.168.11.10'
> mount.nfs: text-based options: 'addr=192.168.11.10'
> mount.nfs: text-based options: 'addr=192.168.11.10'
>
> Server Version:
> net-fs/nfs-utils
> Latest version available: 1.1.4-r1
> Latest version installed: 1.1.4-r1
> Size of files: 574 kB
> Homepage: http://linux-nfs.org/
> Description: NFS client and server daemons
> License: 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-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-01 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinD01zA=DTXEDG5pXVYcrEGsWOyXcMta0rzvB6n@mail.gmail.com>
2011-02-01 3:24 ` clients cannot reconnect to mounted nfs shares after server restart camden lindsay
2011-02-01 18:15 ` J. Bruce Fields [this message]
2011-02-04 9:31 ` camden lindsay
2011-02-06 20:47 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110201181510.GA25136@fieldses.org \
--to=bfields@fieldses.org \
--cc=camden.lindsay@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).