Re: full data disk -- any chance of recovery

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Gregory S(dot) Williamson" <gsw(at)globexplorer(dot)com>, 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-04 01:03:00
Message-ID: 20060104010300.GA82560@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, Jan 02, 2006 at 12:45:29PM -0500, Tom Lane wrote:
> "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.

Another alternative: most unix filesistems actually set it up so that
there is still some free space left even if it's reporting 100%. On
FreeBSD, you can change the amount of reserved space with tunefs -m, but
you should read the caveats in man tunefs.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Gregory S. Williamson 2006-01-04 01:17:45 Re: full data disk -- any chance of recovery
Previous Message Jim C. Nasby 2006-01-04 00:45:56 Re: migrating oracle table to PostgresQL