Date: Mon, 17 Mar 2003 13:21:19 -0800 (PST) From: "Andrew P. Lentvorski, Jr." <bsder@allcaps.org> To: Steve Sizemore <steve@ls.berkeley.edu> Cc: Dan Nelson <dnelson@allantgroup.com>, <current@FreeBSD.ORG> Subject: Re: NFS file unlocking problem Message-ID: <Pine.LNX.4.44.0303171255310.15683-100000@mail.allcaps.org> In-Reply-To: <20030317060018.GA45288@math.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 16 Mar 2003, Steve Sizemore wrote: > Sorry - I was trying to be too helpful. I actually did capture the raw > dump but appended the decoded output. This time, I've attached a > real raw dump. The dump doesn't seem to be attached. However, I note that the request being sent is SETLKW which is a blocking wait until lock is granted. If the server thinks the file is already locked, it will hang *and* that is the proper behavior. What is the result of running this locally on the NFS server and attempting to lock the underlying file? If rpc.lockd is hanging onto a lock, running that perl script locally on the actual file (not an NFS mounted image of it) should also hang. As a side note, you probably want to create a C executable to do this kind of fcntl fiddling when attempting to test NFS. That way you can use a locally mounted binary and you won't wind up with all of the Perl access calls on the NFS wire. Or, at least, use a local copy of Perl. -a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44.0303171255310.15683-100000>