From: Orion Poplawski <orion@cora.nwra.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: nfs4 mount hanging suddenly
Date: Thu, 01 Mar 2012 08:34:02 -0700 [thread overview]
Message-ID: <4F4F96EA.9050203@cora.nwra.com> (raw)
In-Reply-To: <1330609841.6218.6.camel@lade.trondhjem.org>
On 03/01/2012 06:50 AM, Myklebust, Trond wrote:
> On Wed, 2012-02-29 at 16:21 -0700, Orion Poplawski wrote:
>> On 02/29/2012 04:17 PM, J. Bruce Fields wrote:
>>> On Wed, Feb 29, 2012 at 03:29:36PM -0700, Orion Poplawski wrote:
OMP Reply (Call
>>>
>>> That probably means the server is waiting for the client to return a
>>> delegation.
>>>
>>> Either the server's confused about their being a delegation, or the
>>> client's failing to return one it should?
>>>
>
> As far as I can see from your trace, the client keeps trying to open the
> file '.history', and the server keeps replying with NFS4ERR_DELAY. There
> is nothing in the trace itself that can tell us why the server is
> delaying.
So, it seems to be on the server side? I didn't get any relief
restarting nfs on the server. Any way to trace what is happening on the
server side?
Thanks again.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
next prev parent reply other threads:[~2012-03-01 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 22:29 nfs4 mount hanging suddenly Orion Poplawski
2012-02-29 23:17 ` J. Bruce Fields
2012-02-29 23:21 ` Orion Poplawski
2012-03-01 13:50 ` Myklebust, Trond
2012-03-01 15:34 ` Orion Poplawski [this message]
2012-03-01 19:28 ` 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=4F4F96EA.9050203@cora.nwra.com \
--to=orion@cora.nwra.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.