From owner-freebsd-current Tue Mar 18 14:50:56 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AAE237B401 for ; Tue, 18 Mar 2003 14:50:54 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 367E643FA3 for ; Tue, 18 Mar 2003 14:50:51 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0203.cvx22-bradley.dialup.earthlink.net ([209.179.198.203] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18vPuw-0002e1-00; Tue, 18 Mar 2003 14:50:47 -0800 Message-ID: <3E77A275.4F4B5B1F@mindspring.com> Date: Tue, 18 Mar 2003 14:49:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Steve Sizemore Cc: current@freebsd.org Subject: Re: NFS file unlocking problem References: <3E768C47.229C1DF0@mindspring.com> <20030318065716.GB99408@math.berkeley.edu> <3E76CC9A.BBAAED4A@mindspring.com> <20030318172237.GA320@math.berkeley.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c02ff085df222b2c519783fbf0a8c897666fa475841a1c7a350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Steve Sizemore wrote: > I don't see now it could be "inter-program", since I've gone to great > lengths to simplify it to a single program failing on a brand new file. Is the file ever open by a program on the NFS server itself? If so, this can cause the behaviour you are seeing (if you are interested in the technical reasons, there's a different posting). > Oh, so that's what that meant. :-) But (see above) it's pretty clear > to me that nothing else could have it locked. Then you aren't getting the error. 8-) 8-) 8-). > > Once you know that, you can go hit them over the head with a > > large baseball bat. 8-). > > Yes. But that somebody is undoubtedly not a real person. kill -9 them, then. > > But I think it may be as simple as you not telling us that you > > have multiple IP addresses configured on one of your machines? > > No, but this might be an important clue. The FreeBSD host has multiple > (2) A Records in the DNS. In fact, I think that when it last worked, > it had only a single A Record. Well, try undoing that change. I don't think that's it, though, but it gives you a lever to pull. > Also, I notice that there are two > rpc.lockd processes running on the FreeBSD server. I hadn't noticed > that before it started failing, but I didn't mention it, since > rpc.lockd does get invoked twice in rc.network. However, rpc.statd > also gets called twice, and there's only a single version of it > running... Not the problem, I think. > > If so, try: > > > > sysctl -w net.inet.ip.check_interface=0 > > What does this do, just turn off checking? Can I do this on the > running system, or do I need to put it into sysctl.conf and reboot? > (BTW, from the man page - > "The -w option has been deprecated and is silently ignored.") Use it on a running system. Ignore the warning. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message