On Tue, 2009-08-25 at 00:12 +0100, Daniel J Blueman wrote: > Perhaps unrelated to the manager kthread, I reproduced a > "nfs4_reclaim_open_state: Lock reclaim failed!" message ultimately - > expected/significant? It is not unexpected in a situation where you lose connection with the server. Another client is then free step in and grab the lock. We should probably be issuing a SIGLOST to the process and clear the page cache in this situation. Currently, we cravenly write out the data despite the fact that we're no longer holding a lock... Cheers Trond -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- 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
