pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Frost <jeff@frostconsultingllc.com>
To: 'Gregory S. Williamson' <gsw@globexplorer.com>
To: pgsql-admin@postgresql.org
Subject: Re: full data disk -- any chance of recovery
Date: Sun, 1 Jan 2006 23:49:37 -0800
Message-ID: <006a01c60f71$14c12080$800101df@jefflap> (raw)
In-Reply-To: <71E37EF6B7DCC1499CEA0316A2568328024BBD82@loki.wc.globexplorer.net>

Greg, I'm not sure what you're looking for in the way of suggestions.  Do
you just want to be able to start this postgres server up and remove some
data?  Easiest way I see to accomplish that given the information you
provided is to move pg_xlog to the sda disk and symlink it to the data dir.


In general terms, it would go like this:

Stop postmaster
cd /data/gex_runtime
mv pg_xlog /
ln -s /pg_xlog
Start postmaster

The commands may vary depending on OS.

That would also give you better performance if sda and sdb are actually
separate physical disks.  However, that's only going to give you about 500MB
of free space, so I see bigger disks in your future.  A vacuum full might
recover a bit of space as well if you've got any bloat.

The question I have is this: Is your database read-only?  Otherwise,
bringing these machines back up probably isn't too useful as they are now
out of sync with the new primary (your old hot spare).

Good luck!

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Gregory S. Williamson
Sent: Sunday, January 01, 2006 11:28 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] full data disk -- any chance of recovery

Availables space is:
$ df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1             32850580   3137552  28044280  11% /
/dev/sdb1             35001508  33223500        16 100% /data

Any suggestions ? Falling back to the last known state is fine, but just in
case I am making a backup of the remaining database to build a replacement.

And yes, I did forsee this and did warn management repeatedly and yet
somehow the advice falls on deaf ears. Go figure. I guess maybe because it
isn't management that a hole kicked in a 3 day weekend.





view thread (21+ messages)  latest in thread

Message-ID: <006a01c60f71$14c12080$800101df@jefflap>
Permalink:  ../006a01c60f71$14c12080$800101df@jefflap/
Also on:    postgresql.org/message-id/006a01c60f71$14c12080$800101df@jefflap

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jeff@frostconsultingllc.com, gsw@globexplorer.com
  Subject: Re: full data disk -- any chance of recovery
  In-Reply-To: <006a01c60f71$14c12080$800101df@jefflap>
  References: <71E37EF6B7DCC1499CEA0316A2568328024BBD82@loki.wc.globexplorer.net> <006a01c60f71$14c12080$800101df@jefflap>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox