From: Tom Lane <tgl@sss.pgh.pa.us>
To: Medora Schauer <mschauer@fairfield.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: server crash
Date: Tue, 09 Nov 2004 11:53:26 -0500
Message-ID: <20662.1100019206@sss.pgh.pa.us> (raw)
In-Reply-To: <906E2C446A276048A1BE283F17BCB12C01BA8E2B@encounter.fairind.fairfield.com>
References: <906E2C446A276048A1BE283F17BCB12C01BA8E2B@encounter.fairind.fairfield.com>
"Medora Schauer" <mschauer@fairfield.com> writes:
> PG: 7.3
I hope you meant "7.3.8", or at least something later than original 7.3 ;-)
> PANIC: link from /data/database/pg_xlog/00000001000000D9 to /data/database/pg_xlog/00000001000000E1 (initialization of log file 1, segment 225) failed: No such file or directory
AFAICS, the only way that that message could come out is if
a readdir() scan of /data/database/pg_xlog found a file named
00000001000000D9 but then an immediately following link() call
didn't find it. This suggests filesystem corruption to me;
it might be worth running fsck. Also check whether your kernel
is reasonably up to date, as it could be a kernel bug.
The fact that the subsequent startup process failed again in just the
same way seems to eliminate most of the theories that would suggest
it's a Postgres bug. In particular, it isn't a race condition such as
two processes trying to delete the same file at the same time, because
the recovery startup sequence does no parallel processing.
regards, tom lane
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: tgl@sss.pgh.pa.us, mschauer@fairfield.com
Subject: Re: server crash
In-Reply-To: <20662.1100019206@sss.pgh.pa.us>
* 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