DB errors
We had a crash of one of our db systems last night. After doing a fsck of
he file system and getting the db backup, we're getting a lot of these
messages in our logs. The DB will also occasionally crash now.
Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR: could
not access status of transaction 2259991368
Oct 12 07:40:16 postgres[30770]: [3-2] 2007-10-12 07:40:16 PDTDETAIL: Could
not read from file "pg_clog/086B" at offset 73728: Success.
Any ideas?
Thanks,
Akash
On 10/12/07, Akash Garg <akash.garg@gmail.com> wrote:
We had a crash of one of our db systems last night. After doing a fsck of
he file system and getting the db backup, we're getting a lot of these
messages in our logs. The DB will also occasionally crash now.Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR: could
not access status of transaction 2259991368
Oct 12 07:40:16 postgres[30770]: [3-2] 2007-10-12 07:40:16 PDTDETAIL: Could
not read from file "pg_clog/086B" at offset 73728: Success.
Got a recent backup?
IT sounds like your db is corrupted, and while recovering some of the
data in it might be possible, it would be better to start over with a
clean backup.
Note that if your database acts like this after a crash, you are
likely running with unreliable fsyncs on your system (either they were
turned on in postgresql.conf or your hardware lies to the OS). That's
bad. A properly built postgresql server should be capable of
recovering from this with no corruption.
2007/10/12, Akash Garg <akash.garg@gmail.com>:
We had a crash of one of our db systems last night. After doing a fsck of
he file system and getting the db backup, we're getting a lot of these
messages in our logs. The DB will also occasionally crash now.Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR: could
not access status of transaction 2259991368
Oct 12 07:40:16 postgres[30770]: [3-2] 2007-10-12 07:40:16 PDTDETAIL: Could
not read from file "pg_clog/086B" at offset 73728: Success.
which version are you using?
--
Filip Rembiałkowski
8.2
Show quoted text
On 10/12/07, Filip Rembiałkowski <plk.zuber@gmail.com> wrote:
2007/10/12, Akash Garg <akash.garg@gmail.com>:
We had a crash of one of our db systems last night. After doing a fsck
of
he file system and getting the db backup, we're getting a lot of these
messages in our logs. The DB will also occasionally crash now.Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16
PDTERROR: could
not access status of transaction 2259991368
Oct 12 07:40:16 postgres[30770]: [3-2] 2007-10-12 07:40:16PDTDETAIL: Could
not read from file "pg_clog/086B" at offset 73728: Success.
which version are you using?
--
Filip Rembiałkowski
On Friday 12 October 2007, "Akash Garg" <akash.garg@gmail.com> wrote:
We had a crash of one of our db systems last night. After doing a fsck
of he file system and getting the db backup, we're getting a lot of these
messages in our logs. The DB will also occasionally crash now.Oct 12 07:40:16 postgres[30770]: [3-1] 2007-10-12 07:40:16 PDTERROR:
could not access status of transaction 2259991368
Oct 12 07:40:16 postgres[30770]: [3-2] 2007-10-12 07:40:16 PDTDETAIL:
Could not read from file "pg_clog/086B" at offset 73728: Success.Any ideas?
Restore from backup. And find out why your server doesn't respect fsync.
--
The global consumer economy can best be described as the most efficient way
to convert natural resources into waste.