From: | "Josh Tolley" <eggyknap(at)gmail(dot)com> |
---|---|
To: | "Zoltan Boszormenyi" <zb(at)cybertec(dot)at> |
Cc: | "Phoenix Kiula" <phoenix(dot)kiula(at)gmail(dot)com>, "Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: URGENT: Whole DB down ("no space left on device") |
Date: | 2007-08-31 13:17:36 |
Message-ID: | e7e0a2570708310617i34660762y7ddf6e8943b642bd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/31/07, Zoltan Boszormenyi <zb(at)cybertec(dot)at> wrote:
> Phoenix Kiula írta:
> > I am getting this message when I start the DB:
> >
> >
> > psql: FATAL: could not access status of transaction 0
> > DETAIL: Could not write to file "pg_subtrans/01F8" at offset 221184:
> > No space left on device.
> >
> >
> > What is this about and how do I solve this? A "df -h" on my system shows this:
> >
> >
> > Filesystem Type Size Used Avail Use% Mounted on
> > ...
> > /dev/sda2 ext3 9.9G 9.5G 0 100% /var
> >
In addition to what others have already said, when things calm down
you should consider implementing some sort of monitoring system that
is configured to start screaming before you run into problems like
this. At my place of work, we've set up Nagios to monitor the space
left on various partitions, and email us when a partition gets above
90% full.
- eggyknap
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Tolley | 2007-08-31 13:33:36 | Re: Obtaining random rows from a result set |
Previous Message | Zoltan Boszormenyi | 2007-08-31 12:56:05 | Re: URGENT: Whole DB down ("no space left on device") |