From owner-freebsd-questions Thu Sep 3 16:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16867 for freebsd-questions-outgoing; Thu, 3 Sep 1998 16:29:33 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16852; Thu, 3 Sep 1998 16:29:29 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA16333; Thu, 3 Sep 1998 16:28:20 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd016306; Thu Sep 3 16:28:18 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA05167; Thu, 3 Sep 1998 16:28:08 -0700 (MST) From: Terry Lambert Message-Id: <199809032328.QAA05167@usr09.primenet.com> Subject: Re: .nfs files, what causes them and why do they hang around? To: mike@smith.net.au (Mike Smith) Date: Thu, 3 Sep 1998 23:28:08 +0000 (GMT) Cc: jay@oneway.com, questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199809031124.LAA00428@dingo.cdrom.com> from "Mike Smith" at Sep 3, 98 11:24:03 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a fairly high-traffic NFS server running FreeBSD 2.2.6 > > using nfsv3 to all FreeBSD 2.2.6 clients. One of the things that I notice > > on it is that there are hundreds of .nfsA3d7a4.4 files hanging around. I > > know that these are some type of nfs temporary files, and that they are > > normally supposed to be removed, but I have some on there from August > > 17th. I have removed them without problem before, but I am curious as to > > what is causing them, and wondering if it is related to another problem we > > are having. > > They're files that have been unlinked but not closed on the client; > because NFS is stateless they can't be unlinked on the server (there's > no indication that the client has the file open, because there's no > state...). > > You'll normally get these if the client goes down unexpectedly. Note that if the server goes down *and* the client goes down, you may be left with "stale" versions of these files, which you then have to manually remove. As a general rule, you should "find" files matching this name format and older than twice the longest reasonable expected use of an unlinked file by a client to delete them. The others may still be in use. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message