On Mon, 3 Jul 2006, Kostik Belousov wrote:
On Mon, Jul 03, 2006 at 12:50:11AM -0400, Francisco Reyes wrote:
Kostik Belousov writes:
Since nobody except you experience that problems (at least, only you
notified
about the problem existence)
Did you miss the part of:
User Freebsd writes:
Since there are several of us experiencing what looks to be the same sort
of deadlock issue, I beseech you not to give up
I am not the only one reporting or having the issue.
I think you have different issues.
I agree. It looks like we have several issues floating around. There are
some known issues with rpc.lockd (and probably some unknown ones) that will
require a concerted effort to resolve. There appear to be a number of reports
relating to this/these problems.
It sounds like there is also an NFS client race condition or other bug of some
sort.
I think it would be really useful to isolate the two during debugging.
Specifically, to make sure that the second client bug is reproduceable without
rpc.lockd running on the client (and related mount flags). Once we have some
more information, such as vnode locking information, client thread stack
traces, etc, we should probably get Mohan in the loop if things seem sticky.
I believe he was on vacation last week; he may be back this week sometime.
With the July 4 weekend afoot, a lot of .us developers are offline.
Robert N M Watson
Computer Laboratory
University of Cambridge
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
