Date: Sat, 8 Apr 2006 01:28:55 -0400 From: "Rong-En Fan" <grafan@gmail.com> To: "Jun Kuriyama" <kuriyama@imgsrc.co.jp> Cc: stable@freebsd.org Subject: Re: rpc.lockd brokenness (2) Message-ID: <6eb82e0604072228o601b44e2n2d8a718d0b33664f@mail.gmail.com> In-Reply-To: <7mveururc6.wl%kuriyama@imgsrc.co.jp> References: <7mveururc6.wl%kuriyama@imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/6/06, Jun Kuriyama <kuriyama@imgsrc.co.jp> wrote: > > I'm not yet received enough information to track rpc.lockd problem. > > As Kris posted before, here is a patch to backout my suspected > commit. If someone can easily reproduce this problem, please try with > this patch on both of server/client side of rpc.lockd (I'm not sure > which of server/client side this affects). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/80389 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/84953 > > Any reports about this patch (OK or still problem) are welcome! Hi, Somehow I have problems with lockd after 3 boxes upgraded from Feb's RELENG_6 to Apr 6's. One of them has problems with lockd. For example, mutt and irssi will stuck in lockd (shown by top). I tried to back out changes in revision 1.18 for lock_proc.c, and do /etc/rc.d/nfslocking stop then a start. After backout it, mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck in lockd again. Last month, I played with the test program/script in those two PRs, found that revision 1.18 does not make any difference. I'm not 100% sure the problem I encountered now is related to rev 1.18. But it is a report that backout 1.18 really helps. For record, all my clients involved in this mail are running RELENG_6. Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6. Regards, Rong-En Fan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e0604072228o601b44e2n2d8a718d0b33664f>