X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 93BCE528D1; Fri, 3 Jun 2005 00:30:15 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08839-03; Fri, 3 Jun 2005 03:29:53 +0000 (GMT) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by svr1.postgresql.org (Postfix) with ESMTP id 3130552861; Fri, 3 Jun 2005 00:29:51 -0300 (ADT) Received: from mortis.over-yonder.net (adsl-144-206-250.jan.bellsouth.net [70.144.206.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id C549D4A; Thu, 2 Jun 2005 22:29:48 -0500 (CDT) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 96D8121028; Thu, 2 Jun 2005 22:29:47 -0500 (CDT) Date: Thu, 2 Jun 2005 22:29:47 -0500 From: "Matthew D. Fuller" To: "Marc G. Fournier" Cc: pgsql-admin@postgresql.org Subject: Re: Network Storage Devices / NFS ... Message-ID: <20050603032947.GB3092@over-yonder.net> References: <20050602220617.Q933@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050602220617.Q933@ganymede.hub.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/7 X-Sequence-Number: 17762 On Thu, Jun 02, 2005 at 10:19:38PM -0300 I heard the voice of Marc G. Fournier, and lo! it spake thus: > > Anyone actually dealing with a configuration using this for your > data drives? I'm looking for more details on what exactly they are > using for the NFS server, but I have a client reporting that their > pg_xlog directory is *full* of .nfs* files that are 'months old' ... > I'm suspecting that this is some sort of temp file that the NFS > itself is creating, and is safe to just delete, but am wondering if > someone out there knows more definitively ... ? As I recall, that's a side-effect of deleting files on NFS, because of the statelessness. If one client has a file open, and another client deletes it, or two processes on the same client have it open and deleted respectively, or something on the server... I can't remember which case it is. But they're renames of files that were "deleted". If nothing has them open (fstat or lsof or something) they should be safe to delete (but don't blame me if it blows up!). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.