All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: pNFS timeouts
Date: Mon, 14 Jun 2010 10:46:55 -0400	[thread overview]
Message-ID: <4C1640DF.5070506@panasas.com> (raw)
In-Reply-To: <20100614142332.GB17703@ics.muni.cz>

On Jun. 14, 2010, 10:23 -0400, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:
> Hi,
> 
> On Mon, Jun 14, 2010 at 10:11:30AM -0400, Benny Halevy wrote:
>> I'm not sure if that explains the 15 seconds delay.
>> I wonder if it could be related to the nfsv4 grace period.
>> Does this happen if you wait for a couple minutes after
>> the server restarts before starting the test?
> 
> I repeated the test after approx. 6 hours the server was restarted and it is
> the same, the delay still happens. 
> 
> But it could be something related, it complains about lease renewal:
> 
> Jun 14 16:17:00 undomiel1 kernel: [187434.936220] nfs4_renew_state: done
> Jun 14 16:17:00 undomiel1 kernel: [187434.936492] nfs41_sequence_done: Error 0 free the slot
> Jun 14 16:17:00 undomiel1 kernel: [187434.936500] nfs4_free_slot: free_slotid 0 highest_used_slotid -1
> Jun 14 16:17:00 undomiel1 kernel: [187434.936507] nfs41_sequence_call_done rpc_cred ffff88003d7a0300
> Jun 14 16:17:00 undomiel1 kernel: [187434.936514] <-- nfs41_sequence_call_done
> Jun 14 16:17:00 undomiel1 kernel: [187434.936522] nfs4_schedule_state_renewal: requeueing work. Lease period = 60
> Jun 14 16:17:00 undomiel1 kernel: [187434.936530] --> nfs_put_client({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_state_renewal: requeueing work. Lease period = 38

This looks like a complaint but it's actually saying that the "failure"
is due to the fact that everything is OK (lease not expired)

BTW, is this the same issue that Jiri reported?
http://marc.info/?l=linux-nfs&m=127619696004097&w=2

Benny

> 
> The full log can be found at:
> http://undomiel.ics.muni.cz/tmp/nfs-log.txt
> 

  reply	other threads:[~2010-06-14 14:46 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 [this message]
2010-06-14 15:02       ` Benny Halevy
2010-06-14 15:12         ` Lukas Hejtmanek
2010-06-14 15:05       ` Lukas Hejtmanek
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=4C1640DF.5070506@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=xhejtman@ics.muni.cz \
    /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.