Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TsKIB-0003td-Ec for pgsql-admin@arkaria.postgresql.org; Mon, 07 Jan 2013 21:31:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TsKIA-00005M-IX for pgsql-admin@arkaria.postgresql.org; Mon, 07 Jan 2013 21:31:34 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TsKI9-00005D-J7 for pgsql-admin@postgresql.org; Mon, 07 Jan 2013 21:31:33 +0000 Received: from [64.207.29.137] (helo=mail.illumen.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TsKI6-0001qY-Fz for pgsql-admin@postgresql.org; Mon, 07 Jan 2013 21:31:32 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDED1E.5B2EC120" Subject: Re: Possible database corruption - urgent Date: Mon, 7 Jan 2013 14:31:29 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Possible database corruption - urgent Thread-Index: Ac3tHNaAnSiwoU9uSlew79m2stv9kAAAQLOg From: "Benjamin Krajmalnik" To: "Benjamin Krajmalnik" , X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.207.29.137 (failed) X-Pg-Spam-Score: 1.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. ------_=_NextPart_001_01CDED1E.5B2EC120 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I forgot to mention - PostgreSQL 9.0 - my apologies. Can I just recreate the file using touch so it exists and then restart potgresql? The system coredumped and was attempting to go intorecovery mode =20 =20 2013-01-07 01:49:12 GMT ERROR: could not open file "base/16748/181979366_fsm": No such file or directory 2013-01-07 01:49:12 GMT CONTEXT: writing block 1 of relation base/16748/181979366_fsm 2013-01-07 01:49:12 GMT WARNING: could not write block 1 of base/16748/181979366_fsm . . . =20 2013-01-07 01:49:12 GMT ERROR: could not open file "base/16748/181979366_fsm": No such file or directory 2013-01-07 01:49:12 GMT CONTEXT: writing block 1 of relation base/16748/181979366_fsm 2013-01-07 01:49:12 GMT WARNING: could not write block 1 of base/16748/181979366_fsm =20 =20 From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Benjamin Krajmalnik Sent: Monday, January 07, 2013 2:22 PM To: pgsql-admin@postgresql.org Subject: [ADMIN] Possible database corruption - urgent =20 I have a situation where pg_xlog started growing until it filled up the disk drive. I got alerted to the error and started investigating. Checked the logs and I am seeing the following entry repeatedly: =20 2013-01-07 01:49:12 GMT ERROR: could not open file "base/16748/181979366_fsm": No such file or directory 2013-01-07 01:49:12 GMT CONTEXT: writing block 1 of relation base/16748/181979366_fsm 2013-01-07 01:49:12 GMT WARNING: could not write block 1 of base/16748/181979366_fsm =20 I checked the actual file system, and that file is indeed missing. 181979366 exists. Is there a way to get the system back up and running? I stopped the postmaster and am moving the pg_xlog directory to a partition which has room left in it, but I need to resolve this missing file problem =20 =20 ------_=_NextPart_001_01CDED1E.5B2EC120 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I forgot to mention – PostgreSQL 9.0 = – my apologies.

Can I just recreate the file using touch so it = exists and then restart potgresql?

The system coredumped = and was attempting to go intorecovery mode

 

 

2013-01-07 01:49:12 GMT = ERROR:  could not open file "base/16748/181979366_fsm": = No such file or directory

2013-01-07 01:49:12 GMT = CONTEXT:  writing block 1 of relation = base/16748/181979366_fsm

2013-01-07 01:49:12 GMT WARNING:  could not = write block 1 of base/16748/181979366_fsm

.

.

.

 

2013-01-07 01:49:12 GMT = ERROR:  could not open file "base/16748/181979366_fsm": = No such file or directory

2013-01-07 01:49:12 GMT = CONTEXT:  writing block 1 of relation = base/16748/181979366_fsm

2013-01-07 01:49:12 GMT WARNING:  could not = write block 1 of base/16748/181979366_fsm

 

 

From:= = pgsql-admin-owner@postgresql.org = [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Benjamin = Krajmalnik
Sent: Monday, January 07, 2013 2:22 = PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] = Possible database corruption - = urgent

 

I have a = situation where pg_xlog started growing until it filled up the disk = drive.

I got alerted to the error and = started investigating.

Checked the = logs and I am seeing the following entry repeatedly:

 

2013-01-07 = 01:49:12 GMT ERROR:  could not open file = "base/16748/181979366_fsm": No such file or = directory

2013-01-07 01:49:12 GMT = CONTEXT:  writing block 1 of relation = base/16748/181979366_fsm

2013-01-07 = 01:49:12 GMT WARNING:  could not write block 1 of = base/16748/181979366_fsm

 

I checked = the actual file system, and that file is indeed missing.  181979366 = exists.

Is there a way to get the = system back up and running?

I stopped = the postmaster and am moving the pg_xlog directory to a partition which = has room left in it, but I need to resolve this missing file = problem

 

 

------_=_NextPart_001_01CDED1E.5B2EC120--