All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Harald Dunkel <harald.dunkel@aixigo.de>, linux-nfs@vger.kernel.org
Subject: Re: nfs4_reclaim_open_state: Lock reclaim failed!
Date: Fri, 31 Aug 2018 07:49:50 -0400	[thread overview]
Message-ID: <30d4e07de5d976756857db77ddb17582897ae2bf.camel@kernel.org> (raw)
In-Reply-To: <b4c125d6-be59-6953-bfa7-8ada6f8daa01@aixigo.de>

On Wed, 2018-08-29 at 11:13 +0200, Harald Dunkel wrote:
> PS:
> 
> On 8/29/18 11:09 AM, Harald Dunkel wrote:
> > Hi folks,
> > 
> > dmesg -T shows me a large list of messages
> > 
> > :
> > [Wed Aug 29 11:13:02 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > [Wed Aug 29 11:13:02 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > [Wed Aug 29 11:13:02 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > [Wed Aug 29 11:13:03 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > [Wed Aug 29 11:13:03 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > [Wed Aug 29 11:13:04 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > [Wed Aug 29 11:13:05 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
> > :
> > 
> > with a modification date appr 9 minutes in the future. NFS server and
> 
> Its a "timestamp", of course. Sorry.
> 
> > client have the correct time and are in sync, afaict. How comes?
> > 
> > 
> > Kernel is 4.9.88-1+deb9u1 on the client, 4.16.5-1~bpo9+1 on the NFS server.
> > 
> > 
> > Every helpful comment is highly appreciated.
> > Harri
> > 
> 
> 

Hi Harald,

Usually this means that the client and server have gotten out of sync
(possibly due to a server reboot), the client has tried to reclaim the
state it held before but that reclaim failed.

Determining why that happened is is difficult from the info you have
here. Is your server being restarted regularly? What version of NFS are
you using to mount?

v4.9 is pretty old at this point as well, you may want to try a newer
kernel on the client and see if it behaves better.
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2018-08-31 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  9:09 nfs4_reclaim_open_state: Lock reclaim failed! Harald Dunkel
2018-08-29  9:13 ` Harald Dunkel
2018-08-31 11:49   ` Jeff Layton [this message]
2018-09-03  8:34     ` Harald Dunkel
2018-09-03  9:32       ` Jeff Layton
2018-09-04  7:31         ` Harald Dunkel
2018-09-04 12:11           ` Jeff Layton
2018-08-31 15:41 ` Olga Kornievskaia
2018-09-03  7:48   ` Harald Dunkel
2018-09-03 13:15     ` Olga Kornievskaia

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=30d4e07de5d976756857db77ddb17582897ae2bf.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=harald.dunkel@aixigo.de \
    --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.