Re: full data disk -- any chance of recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com>
Cc: "Jeff Frost" <jeff(at)frostconsultingllc(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: full data disk -- any chance of recovery
Date: 2006-01-02 17:45:29
Message-ID: 7230.1136223929@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Gregory S. Williamson" <gsw(at)globexplorer(dot)com> writes:
> 2006-01-02 00:30:01 LOG: could not close temporary statistics file "/data/postgres/gex_runtime/global/pgstat.tmp.1453": No space left on device
> 2006-01-02 00:33:54 ERROR: could not access status of transaction 0
> DETAIL: could not write to file "/data/postgres/gex_runtime/pg_clog/0AFA" at offset 196608: No space left on device

Just kill -9 all the postgres processes; everything you need should be
safely down in the WAL files.

You might not have to move pg_xlog --- the first thing to do is see
if there are any large temp files hanging about in the pgsql_tmp
subdirectories. Anything you see in there can be shot on sight once
the postmaster is stopped (actually, recent versions of the postmaster
will do it for you on restart, but don't remember about 7.4).

Which PG release is this exactly (7.4.what)? This misbehavior reminds
me of a bug that we fixed in 7.4.2.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message warren little 2006-01-02 19:05:29 Emergency - Need assistance
Previous Message Jeff Frost 2006-01-02 17:20:18 Re: full data disk -- any chance of recovery