Date: Wed, 5 Jul 2006 16:18:08 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Michael Collette <Michael.Collette@TestEquity.com> Cc: freebsd-stable@freebsd.org, User Freebsd <freebsd@hub.org> Subject: Re: NFS Locking Issue Message-ID: <20060705161559.W18236@fledge.watson.org> In-Reply-To: <44A99CC1.7070501@TestEquity.com> References: <20060629230309.GA12773@lpthe.jussieu.fr> <20060630041733.GA4941@zibbi.meraka.csir.co.za> <cone.1151802806.162227.42680.1000@zoraida.natserv.net> <20060702162942.D1103@ganymede.hub.org> <44A99CC1.7070501@TestEquity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 3 Jul 2006, Michael Collette wrote: > --------------------------------------------------------------------- > Let's start with the simplest. The scenario here involves 2 machines, mach01 > and mach02. Both are running 6-STABLE, and both are running rpcbind, > rpc.statd, and rpc.lockd. mach01 has exported /documents and mach02 is > mounting that export under /mnt. Simple enough? > > The /documents directory has multiple subdirectories and files of various > sizes. The actual amount of data doesn't really matter to produce a failure. > All you need to do at this point is to try to copy files from that mount > point to somewhere else on the hard drive. > > cp -Rp /mnt/* /tmp/documents/ > > You may, or not, see that a couple of subdirectories were created, but no > files actually moved over. The cp command is now locked up, and no traffic > moves. This usually takes a second or two to show up as a problem. I can > repeat this with multiple 6-STABLE boxes. > > Turn off rpc.lockd on either the server or client before the cp command, and > things work. I've tried several times to reproduce this, and have not succeeded in doing so. In princple, cp should not be using advisory locks. Could you try running cp under ktrace, and saving the ktrace file somewhere outside of NFS? Something like the following: ktrace -f /usr/tmp/localfile cp -Rp /mnt/* /tmp/documents/ If you are able to reproduce the problem with tracing turned on, a copy of the tracefile would be very helpful. Also, when it locks up, are you able to kill cp using Ctrl-C, and if you hit Ctrl-T while it appears locked, what output do you get? Thanks, Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060705161559.W18236>