From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Benny Halevy <bhalevy@panasas.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: pNFS timeouts
Date: Mon, 14 Jun 2010 17:05:42 +0200 [thread overview]
Message-ID: <20100614150542.GD17703@ics.muni.cz> (raw)
In-Reply-To: <4C1640DF.5070506@panasas.com>
On Mon, Jun 14, 2010 at 10:46:55AM -0400, Benny Halevy wrote:
> > Jun 14 16:17:00 undomiel1 kernel: [187434.936507] nfs41_sequence_ca=
ll_done rpc_cred ffff88003d7a0300
> > Jun 14 16:17:00 undomiel1 kernel: [187434.936514] <-- nfs41_sequenc=
e_call_done
> > Jun 14 16:17:00 undomiel1 kernel: [187434.936522] nfs4_schedule_sta=
te_renewal: requeueing work. Lease period =3D 60
> > Jun 14 16:17:00 undomiel1 kernel: [187434.936530] --> nfs_put_clien=
t({2})
> > Jun 14 16:17:16 undomiel1 kernel: [187450.536014] nfs4_renew_state:=
start
> > Jun 14 16:17:16 undomiel1 kernel: [187450.536045] nfs4_renew_state:=
failed to call renewd. Reason: lease not expired
> > Jun 14 16:17:16 undomiel1 kernel: [187450.536056] nfs4_schedule_sta=
te_renewal: requeueing work. Lease period =3D 38
>=20
> This looks like a complaint but it's actually saying that the "failur=
e"
> is due to the fact that everything is OK (lease not expired)
the state renewal actually starts after 16 seconds after schedule start
renewal for some reason. The nfs_put_client actually starts the renewal=
?
> BTW, is this the same issue that Jiri reported?
> http://marc.info/?l=3Dlinux-nfs&m=3D127619696004097&w=3D2
Yes, but I didn't see any response to that, so I guess his report is no=
t clear
enough.
--=20
Luk=E1=B9 Hejtm=E1nek
next prev parent reply other threads:[~2010-06-14 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 8:51 pNFS timeouts Lukas Hejtmanek
2010-06-14 14:11 ` Benny Halevy
2010-06-14 14:23 ` Lukas Hejtmanek
2010-06-14 14:46 ` Benny Halevy
2010-06-14 15:02 ` Benny Halevy
2010-06-14 15:12 ` Lukas Hejtmanek
2010-06-14 15:05 ` Lukas Hejtmanek [this message]
2010-06-14 15:10 ` Benny Halevy
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=20100614150542.GD17703@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--cc=bfields@fieldses.org \
--cc=bhalevy@panasas.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 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.