pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Korry Douglas <korry.douglas@enterprisedb.com>
To: Reno, Natalie <Natalie.Reno@cchmc.org>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: pg_basebackup - Stale file handle for file under gprof
Date: Fri, 26 Feb 2016 10:51:49 -0500
Message-ID: <56D07495.60806@enterprisedb.com> (raw)
In-Reply-To: <C3CC086845CA824D9CC8D5CF9D5701E786DE17FA@MCEXMB2.chmccorp.cchmc.org>
References: <C3CC086845CA824D9CC8D5CF9D5701E786DE175D@MCEXMB2.chmccorp.cchmc.org>
	<56D06354.2070507@enterprisedb.com>
	<C3CC086845CA824D9CC8D5CF9D5701E786DE17FA@MCEXMB2.chmccorp.cchmc.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>


Nothing wrong with building your own version, but you'll want to disable 
profiling in most cases (the profiling code will noticeably hurt 
performance).  The files in the gprof subdirectory are produced by the 
profiler.

The error message you see (Stale file handle) suggests that you are 
using an NFS-mounted filesystem and that someone may have deleted a 
directory while you were running the backup.  That may be ok, but I 
personally would not trust a backup that reported an error (especially 
if you can't explain the error, which I can't).

          -- Korry

> I am guilty of compiling the code myself and enabling the profiling. I 
> am new to Postgres and was following the previous DBAs work. I now 
> realize this needs to be off and will look to be recompiling the code 
> again. I am thinking I will create a new software home and point the 
> database there.
>
> */Natalie Reno/*
>
> Sr. Database Administrator
>
> Database Infrastructure Team Lead
>
> /BioMedical Informatics/
>
> /Cincinnati Children's Hospital/
>
> natalie.reno@cchmc.org <mailto:natalie.reno@cchmc.org>
>
> 513.803.5370
>
> *From:*Korry Douglas [mailto:korry.douglas@enterprisedb.com]
> *Sent:* Friday, February 26, 2016 9:38 AM
> *To:* Reno, Natalie <Natalie.Reno@cchmc.org>
> *Cc:* pgsql-admin@postgresql.org
> *Subject:* Re: [ADMIN] pg_basebackup - Stale file handle for file 
> under gprof
>
> Did you compile your copy of PostgreSQL 9.5 yourself, and if so, did 
> you enable profiling?  If not, which installer did you use?
>
>
>      -- Korry
>
>     I have just implemented pg_basebackup on my 9.5 PostgreSQL
>     database. I received the following notification:
>
>     pg_basebackup: could not create file
>     "<base_directory>/fullbckp_20160225/gprof/2540/gmon.out": Stale
>     file handle
>
>     Is this an issue or can this be ignored since these are tracing files?
>
>     */Natalie Reno/*
>
>     Sr. Database Administrator
>
>     Database Infrastructure Team Lead
>
>     /BioMedical Informatics/
>
>     /Cincinnati Children's Hospital/
>
>     natalie.reno@cchmc.org <mailto:natalie.reno@cchmc.org>
>
>     513.803.5370
>

view thread (4+ messages)

Message-ID: <56D07495.60806@enterprisedb.com>
Permalink:  ../56D07495.60806@enterprisedb.com/
Also on:    postgresql.org/message-id/56D07495.60806@enterprisedb.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: korry.douglas@enterprisedb.com, Natalie.Reno@cchmc.org
  Subject: Re: pg_basebackup - Stale file handle for file under gprof
  In-Reply-To: <56D07495.60806@enterprisedb.com>

* 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