pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marc G. Fournier <scrappy@postgresql.org>
To: Matthew D. Fuller <fullermd@over-yonder.net>
Cc: Marc G. Fournier <scrappy@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: Network Storage Devices / NFS ...
Date: Fri, 3 Jun 2005 00:45:08 -0300 (ADT)
Message-ID: <20050603004351.B933@ganymede.hub.org> (raw)
In-Reply-To: <20050603032947.GB3092@over-yonder.net>
References: <20050602220617.Q933@ganymede.hub.org>
	<20050603032947.GB3092@over-yonder.net>

On Thu, 2 Jun 2005, Matthew D. Fuller wrote:

> 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!).

This is what I was thinking two (around safeness to delete) ... to be 
absolutely certain, doing a quick maintenance shutdown for the postmaster, 
remove all .nfs* files and then restarting should be safe too ...

Sound about right?

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664



view thread (4+ messages)  latest in thread

Message-ID: <20050603004351.B933@ganymede.hub.org>
Permalink:  ../20050603004351.B933@ganymede.hub.org/
Also on:    postgresql.org/message-id/20050603004351.B933@ganymede.hub.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: scrappy@postgresql.org, fullermd@over-yonder.net
  Subject: Re: Network Storage Devices / NFS ...
  In-Reply-To: <20050603004351.B933@ganymede.hub.org>
  References: <20050602220617.Q933@ganymede.hub.org> <20050603032947.GB3092@over-yonder.net> <20050603004351.B933@ganymede.hub.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox