From: Bram Vandoren <brambi@gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: Chuck Lever <chuck.lever@oracle.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFS client hangs after server reboot
Date: Thu, 30 May 2013 13:09:13 +0200 [thread overview]
Message-ID: <CACQjR_AFS88vWM12JV0y4+wLupTDTSSVxprNijMyC7zNQ0jErA@mail.gmail.com> (raw)
In-Reply-To: <1091403305.30723.1369831764803.JavaMail.root@erie.cs.uoguelph.ca>
On Wed, May 29, 2013 at 2:49 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote:
>
>>
> Good point. Which leads to the question, "When did the server reboot
> relative to the packet capture?". Was it before the capture started or
> sometime during the 4400 seconds when the client wasn't sending anything or ???
The server rebooted in the beginning of the capture. I think the first
packets indicate the server was up but the nfs daemon was not running
any more. After ~4400 seconds the server was again available.
Thanks,
Bram.
next prev parent reply other threads:[~2013-05-30 11:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 15:51 NFS client hangs after server reboot Bram Vandoren
2013-04-09 19:08 ` J. Bruce Fields
2013-04-10 19:33 ` Chuck Lever
2013-04-10 23:23 ` Rick Macklem
2013-04-11 23:15 ` Rick Macklem
2013-04-12 9:19 ` Bram Vandoren
2013-04-12 15:10 ` J. Bruce Fields
[not found] ` <CACQjR_CcKwHU8sMrmQ5YfgV5dbuiMLRRqBkDRQEVq2yjGEuzmg@mail.gmail.com>
2013-04-12 15:14 ` Chuck Lever
2013-05-28 12:31 ` Bram Vandoren
2013-05-28 19:23 ` Chuck Lever
2013-05-28 22:06 ` Rick Macklem
2013-05-28 23:30 ` Rick Macklem
2013-05-29 1:04 ` Chuck Lever
2013-05-29 1:13 ` Chuck Lever
2013-05-29 12:49 ` Rick Macklem
2013-05-30 11:09 ` Bram Vandoren [this message]
2013-05-30 0:24 ` Rick Macklem
2013-05-30 0:31 ` Rick Macklem
2013-05-30 11:20 ` Bram Vandoren
2013-05-30 11:04 ` Bram Vandoren
2013-05-30 11:55 ` Rick Macklem
2013-05-31 16:35 ` Bram Vandoren
2013-05-31 23:24 ` Rick Macklem
2013-08-28 13:39 ` William Dauchy
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=CACQjR_AFS88vWM12JV0y4+wLupTDTSSVxprNijMyC7zNQ0jErA@mail.gmail.com \
--to=brambi@gmail.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rmacklem@uoguelph.ca \
/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).