On Thu, Nov 17, 2016 at 05:45:52PM +0000, Trond Myklebust wrote: > On Thu, 2016-11-17 at 11:31 -0500, J. Bruce Fields wrote: > > On Wed, Nov 16, 2016 at 02:55:05PM -0600, Jason L Tibbitts III wrote: > > > > > > I'm replying to a rather old message, but the issue has just now > > > popped > > > back up again. > > > > > > To recap, a client stops being able to access _any_ mount on a > > > particular server, and "NFS: nfs4_reclaim_open_state: Lock reclaim > > > failed!" appears several hundred times per second in the kernel > > > log. > > > The load goes up by one for ever process attempting to access any > > > mount > > > from that particular server. Mounts to other servers are fine, and > > > other clients can mount things from that one server without > > > problems. > > > > > > When I kill every process keeping that particular mount active and > > > then > > > umount it, I see: > > > > > > NFS: nfs4_reclaim_open_state: unhandled error -10068 > > > > NFS4ERR_RETRY_UNCACHED_REP. > > > > So, you're using NFSv4.1 or 4.2, and the server thinks that the > > client > > has reused a (slot, sequence number) pair, but the server doesn't > > have a > > cached response to return. > > > > Hard to know how that happened, and it's not shown in the below. > > Sounds like a bug, though. > > ...or a Ctrl-C.... How does that happen? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
