| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ERROR: xlog flush request not satisfied |
| Date: | 2006-03-07 03:04:26 |
| Message-ID: | 12413.1141700666@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> I'm seeing the following error in 7.4.6. It first surfaced
> after remounting a SAN mount from one box to another and
> then running 'vacuum full':
> pg_dump: ERROR: xlog flush request 68/7D853080 is not satisfied --- flushed only to 0/15A90A8
> CONTEXT: writing block 34 of relation 17156/1470533
What this looks like to me is corrupt data in a page's LSN field (the
first 8 bytes of the page). The LSN is evidently far larger than it
should be. You might try dumping out the indicated page with
pg_filedump (or even just dd/od) to see if anything obvious jumps out.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-07 03:33:54 | Re: Is the "ACCESS EXCLUSIVE" lock for TRUNCATE really necessary? |
| Previous Message | Tom Lane | 2006-03-07 02:39:18 | Re: problem with overloading the "coalesce" function |