Strange error while executing query from front end:

Exact message of my second problem is:

WARNING: relation "rawlog" page 0 is uninitialized --- fixing

-----Original Message-----
From: Mavinakuli, Prasanna (STSD)
Sent: Monday, January 16, 2006 9:28 AM
To: pgsql-general@postgresql.org
Subject: Strange error while executing query from front end:

Hi,

I am getting following strange errors while executing queries.

1)
ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60
CONTEXT: writing block 2 of relation 17142/16653
WARNING: could not write block 2 of 17142/16653
DETAIL: Multiple failures --- write error may be permanent.
ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60
CONTEXT: writing block 2 of relation 17142/16653
WARNING: could not write block 2 of 17142/16653
DETAIL: Multiple failures --- write error may be permanent.
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection

2)I am getting messages saying that

WARNING: relation page <number> is uninitialized in <tablename>

I am getting this WARNING multiple times...

Could u please help me regarding these issues,

Thanking You in advance,
Prasanna.

When I try to do vacuum then also I am getting same error,warning
rather.

LOGARCHDB=# vacuum;
WARNING: relation "rawlog" page 2 is uninitialized --- fixing
WARNING: relation "rawlog" page 3 is uninitialized --- fixing
WARNING: relation "rawlog" page 2 is uninitialized --- fixing
WARNING: relation "rawlog" page 4 is uninitialized --- fixing
WARNING: relation "rawlog" page 3 is uninitialized --- fixing
WARNING: relation "rawlog" page 5 is uninitialized --- fixing
WARNING: relation "rawlog" page 4 is uninitialized --- fixing
WARNING: relation "rawlog" page 6 is uninitialized --- fixing
WARNING: relation "rawlog" page 5 is uninitialized --- fixing
WARNING: relation "rawlog" page 7 is uninitialized --- fixing
WARNING: relation "rawlog" page 6 is uninitialized --- fixing
WARNING: relation "rawlog" page 8 is uninitialized --- fixing
WARNING: relation "rawlog" page 7 is uninitialized --- fixing
WARNING: relation "rawlog" page 9 is uninitialized --- fixing
WARNING: relation "rawlog" page 8 is uninitialized --- fixing
WARNING: relation "rawlog" page 10 is uninitialized --- fixing
WARNING: relation "rawlog" page 9 is uninitialized --- fixing
WARNING: relation "rawlog" page 11 is uninitialized --- fixing
WARNING: relation "rawlog" page 10 is uninitialized --- fixing
WARNING: relation "rawlog" page 12 is uninitialized --- fixing
WARNING: relation "rawlog" page 11 is uninitialized --- fixing
WARNING: relation "rawlog" page 13 is uninitialized --- fixing
WARNING: relation "rawlog" page 12 is uninitialized --- fixing
WARNING: relation "rawlog" page 14 is uninitialized --- fixing
WARNING: relation "rawlog" page 13 is uninitialized --- fixing
WARNING: relation "rawlog" page 15 is uninitialized --- fixing
WARNING: relation "rawlog" page 14 is uninitialized --- fixing
WARNING: relation "rawlog" page 16 is uninitialized --- fixing
WARNING: relation "rawlog" page 15 is uninitialized --- fixing
WARNING: relation "rawlog" page 17 is uninitialized --- fixing
WARNING: relation "rawlog" page 16 is uninitialized --- fixing
WARNING: relation "rawlog" page 18 is uninitialized --- fixing
WARNING: relation "rawlog" page 17 is uninitialized --- fixing
WARNING: relation "rawlog" page 19 is uninitialized --- fixing
WARNING: relation "rawlog" page 18 is uninitialized --- fixing
WARNING: relation "rawlog" page 20 is uninitialized --- fixing
WARNING: relation "rawlog" page 19 is uninitialized --- fixing
WARNING: relation "rawlog" page 21 is uninitialized --- fixing
WARNING: relation "rawlog" page 20 is uninitialized --- fixing
WARNING: relation "rawlog" page 22 is uninitialized --- fixing
WARNING: relation "rawlog" page 21 is uninitialized --- fixing
WARNING: relation "rawlog" page 23 is uninitialized --- fixing
WARNING: relation "rawlog" page 22 is uninitialized --- fixing
WARNING: relation "rawlog" page 24 is uninitialized --- fixing
WARNING: relation "rawlog" page 23 is uninitialized --- fixing
WARNING: relation "rawlog" page 25 is uninitialized --- fixing
WARNING: relation "rawlog" page 24 is uninitialized --- fixing
WARNING: relation "rawlog" page 26 is uninitialized --- fixing
WARNING: relation "rawlog" page 25 is uninitialized --- fixing
WARNING: relation "rawlog" page 27 is uninitialized --- fixing
WARNING: relation "rawlog" page 26 is uninitialized --- fixing
WARNING: relation "rawlog" page 28 is uninitialized --- fixing
WARNING: relation "rawlog" page 27 is uninitialized --- fixing
WARNING: relation "rawlog" page 29 is uninitialized --- fixing
WARNING: relation "rawlog" page 28 is uninitialized --- fixing
WARNING: relation "rawlog" page 30 is uninitialized --- fixing
WARNING: relation "rawlog" page 29 is uninitialized --- fixing
WARNING: relation "rawlog" page 31 is uninitialized --- fixing
WARNING: relation "rawlog" page 30 is uninitialized --- fixing
WARNING: relation "rawlog" page 32 is uninitialized --- fixing
WARNING: relation "rawlog" page 31 is uninitialized --- fixing
WARNING: relation "rawlog" page 33 is uninitialized --- fixing
WARNING: relation "rawlog" page 32 is uninitialized --- fixing
WARNING: relation "rawlog" page 33 is uninitialized --- fixing
VACUUM
LOGARCHDB=#

-----Original Message-----
From: Mavinakuli, Prasanna (STSD)
Sent: Monday, January 16, 2006 10:12 AM
To: pgsql-general@postgresql.org
Subject: RE: Strange error while executing query from front end:

Exact message of my second problem is:

WARNING: relation "rawlog" page 0 is uninitialized --- fixing

-----Original Message-----
From: Mavinakuli, Prasanna (STSD)
Sent: Monday, January 16, 2006 9:28 AM
To: pgsql-general@postgresql.org
Subject: Strange error while executing query from front end:

Hi,

I am getting following strange errors while executing queries.

1)
ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60
CONTEXT: writing block 2 of relation 17142/16653
WARNING: could not write block 2 of 17142/16653
DETAIL: Multiple failures --- write error may be permanent.
ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60
CONTEXT: writing block 2 of relation 17142/16653
WARNING: could not write block 2 of 17142/16653
DETAIL: Multiple failures --- write error may be permanent.
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection

2)I am getting messages saying that

WARNING: relation page <number> is uninitialized in <tablename>

I am getting this WARNING multiple times...

Could u please help me regarding these issues,

Thanking You in advance,
Prasanna.

On Mon, Jan 16, 2006 at 09:27:30AM +0530, Mavinakuli, Prasanna (STSD) wrote:

Hi,

I am getting following strange errors while executing queries.

1)
ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60

If I had to guess, I'd say you're having a hard disk failure of some
kind. In particular, this tells you that a flush of the write ahead
log isn't completing. That's a Bad Thing.

A

--
Andrew Sullivan | ajs@crankycanuck.ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well.
--Dennis Ritchie

Andrew Sullivan <ajs@crankycanuck.ca> writes:

On Mon, Jan 16, 2006 at 09:27:30AM +0530, Mavinakuli, Prasanna (STSD) wrote:

ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60

If I had to guess, I'd say you're having a hard disk failure of some
kind. In particular, this tells you that a flush of the write ahead
log isn't completing. That's a Bad Thing.

Actually it looks like corrupt data to me: some page's LSN field
contains a value that is past the actual end of WAL, and therefore
isn't a correct copy of the location of the last WAL record affecting
that page, as it's supposed to be.

Could have resulted from a hardware error, but it's hard to tell.

regards, tom lane