Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aZKi7-0003td-IY for pgsql-admin@arkaria.postgresql.org; Fri, 26 Feb 2016 15:53:44 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aZKi6-0005zx-Tx for pgsql-admin@arkaria.postgresql.org; Fri, 26 Feb 2016 15:53:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aZKgP-00048O-Ag for pgsql-admin@postgresql.org; Fri, 26 Feb 2016 15:51:57 +0000 Received: from mail-qg0-x230.google.com ([2607:f8b0:400d:c04::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aZKgM-0006Cm-By for pgsql-admin@postgresql.org; Fri, 26 Feb 2016 15:51:55 +0000 Received: by mail-qg0-x230.google.com with SMTP id b67so68085142qgb.1 for ; Fri, 26 Feb 2016 07:51:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to; bh=sdx94/DjLpgdtvwJPMAZ3F/v0/aYLrwtb3QNpPle2RQ=; b=qK1yAGNyuB7xaZ2gBrnElwt+YSYQUZ818h2oaXn7iaGp5fP4qhcCLpa1NupmpkQ/qN 5gTQ1nvIAZM5IoZ3yuM0S+6a7VoAGE3jQHEi8F7auGeuNzyoqHdUyJnuhmgFyxJltro1 zrefcPj+HUumIyiEPRi5yc7QgRvwY8q+HMqRO6k0a91hK7EKqUxV7Xw6WMlEh0ziE3ti SIZY2//uN49PVpcN0fE9bKiELyQBDl4xRftJNHlPVNnFaLKnpfXsCtQ8c4AR1osnKCk1 ATAyuOpMR1R9jtYJBZOZKt2B0C4DfTR8rhAqBVxzs9qjfOaq7lAYKU3tCBpJwCYow1sP D/pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to; bh=sdx94/DjLpgdtvwJPMAZ3F/v0/aYLrwtb3QNpPle2RQ=; b=WJbgeGNBEkgSZcSEb9zgOz6ofrAC5UBJs+eUdQ0l71MmDGD5aTXirPUwNe9q22Ec65 rU1ordhG2R5fsq8kd6Y4DCJsaKVO62a56YEpsPOGPRBPw26pVY+yUCOQeOx5RfwgA2Vy fA/YapTfOqMDQ2dHrnSWmYNh1MeNqKy2dmJPY3zlaStM5Y7uo40OiXyJXBydAIDn7NLL BztGQlWJJ+cr2NfedRo97SgC7sivTgiCW2XhvPJj8ba4mDI624w7cwi59ibxU7yEPuhG +bA0cBUZ/i+f9RTxtp7BifuGNj7FRl1UKdIkajNyC07ElOby1GfJOQLgm6MFlbFRG+C3 9cbg== X-Gm-Message-State: AD7BkJJhcbalz/fLpHoaCM/H4WXVAegEGsRinFMld0OEcUnmMlKbLTS80HwisTTZBeeG8VN+ X-Received: by 10.140.100.244 with SMTP id s107mr2741428qge.19.1456501913030; Fri, 26 Feb 2016 07:51:53 -0800 (PST) Received: from MegaMac.local (va-76-4-65-131.sta.embarqhsd.net. [76.4.65.131]) by smtp.gmail.com with ESMTPSA id v70sm5518611qge.25.2016.02.26.07.51.50 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 26 Feb 2016 07:51:51 -0800 (PST) Message-ID: <56D07495.60806@enterprisedb.com> Date: Fri, 26 Feb 2016 10:51:49 -0500 From: Korry Douglas User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "Reno, Natalie" CC: "pgsql-admin@postgresql.org" Subject: Re: pg_basebackup - Stale file handle for file under gprof References: <56D06354.2070507@enterprisedb.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------050206060009040201020307" X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org This is a multi-part message in MIME format. --------------050206060009040201020307 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 > > 513.803.5370 > > *From:*Korry Douglas [mailto:korry.douglas@enterprisedb.com] > *Sent:* Friday, February 26, 2016 9:38 AM > *To:* Reno, Natalie > *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 > "/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 > > 513.803.5370 > --------------050206060009040201020307 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

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

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

513.803.5370

 

 

 


--------------050206060009040201020307--