Thread: could not write block & xlog flush request 3FD/0 is not satisfied

could not write block & xlog flush request 3FD/0 is not satisfied

From
Yves Weißig
Date:
Hi again pgsql-hackers,

my experimental index which I am developing still has some problems.
Perhaps the list has some advices or hints where this error might occur:

WARNING:  could not write block 6 of base/459204/483963
DETAIL:  Multiple failures --- write error might be permanent.

directly followed by an:

ERROR:  xlog flush request 3FD/0 is not satisfied --- flushed only to
0/20E2DC4
CONTEXT:  writing block 6 of relation base/459204/483963

So far my index worked for small relations, up to 1.000 tuples, now with
a relation of 1.000.000 tuples I am running into these problems. I think
I might be lacking some knowledge to really solve the problem. I am
happy about any suggestions or advices you can make.

Best wishes, Yves


Re: could not write block & xlog flush request 3FD/0 is not satisfied

From
Greg Stark
Date:
On Sun, May 8, 2011 at 4:18 PM, Yves Weißig
<weissig@rbg.informatik.tu-darmstadt.de> wrote:
> ERROR:  xlog flush request 3FD/0 is not satisfied --- flushed only to
> 0/20E2DC4
>

That's a pretty big difference in log positions. It seems likely
you've overwritten the block header writing garbage to the LSN.

--
greg


Re: could not write block & xlog flush request 3FD/0 is not satisfied

From
Yves Weißig
Date:
All right, what would we be the best way to debug such a problem?

Yves

-----Original Message-----
From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Greg Stark
Sent: Sunday, May 08, 2011 6:36 PM
To: weissig@rbg.informatik.tu-darmstadt.de
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] could not write block & xlog flush request 3FD/0 is
not satisfied

On Sun, May 8, 2011 at 4:18 PM, Yves Weißig
<weissig@rbg.informatik.tu-darmstadt.de> wrote:
> ERROR:  xlog flush request 3FD/0 is not satisfied --- flushed only to
> 0/20E2DC4
>

That's a pretty big difference in log positions. It seems likely you've
overwritten the block header writing garbage to the LSN.

--
greg

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers