From: Wendy Cheng <wcheng@redhat.com>
Subject: Re: The host->h_inuse NLM's nlm_gc_hosts()
Date: Thu, 08 Jun 2006 01:52:04 -0400
Message-ID: <1149745924.3379.22.camel@localhost.localdomain>
References: <1149494058.5424.164.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: nfs@lists.sourceforge.net
In-Reply-To: <1149494058.5424.164.camel@localhost.localdomain>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Mon, 2006-06-05 at 03:54 -0400, Wendy Cheng wrote:
> I'm chasing a bug in our distribution - when signalling lockd, the lock
> references do not seem to get released. 

It turns out to be a false alarm. What happened was that we had reports
saying RHCS (Red Hat cluster suite) in some cases would not be able to
umount the filesystem during active-active failover whenever nfs client
was holding posix locks.

Extensive tracing shows the umount failure is actually caused by export
entry's vfsmount reference due to the way unexport was handled. Sending
a signal to lockd *did* release the posix locks as expected.

On the other hand, we do have some other NLM issues (with patches) that
we would like to discuss with the list. More on that later.


-- Wendy


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs