Re: no space left on device

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: "Aurangzeb M(dot) Agha" <ama-list(at)mltp(dot)com>
Cc: PostgreSQL General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: no space left on device
Date: 2004-01-10 00:32:35
Message-ID: Pine.LNX.4.21.0401100030160.29683-100000@ponder.fairway2k.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 9 Jan 2004, scott.marlowe wrote:

> On Fri, 9 Jan 2004, Aurangzeb M. Agha wrote:
>
> > Right! Thus my quandry.
> >
> > Re inodes, how can I check this? But why would this be? Is Postgres
> > sucking up inodes just sitting there as a read-only DB?
>
> If you are out of inodes, I seriously doubt it is Postgresql's fault, as
> you seem to be running everything on the root partition here, it could be
> any other process more likely than postgresql is using all the inodes.
> Basically, when you make a lot of small files you can run out of inodes.

And a common culprit is whatever is being used for usenet caching/serving...or
ordinary mail which is just accumulating in /var/mail (or whereever).

> Since postgresql tends to make a few rather large files, it's usually not
> a concern.
>
> df -i shows inode usage.
>
> On linux, you can change the % reserved for root to 1% with tune2fs:
>
> tune2fs -m 1

--
Nigel J. Andrews

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nigel J. Andrews 2004-01-10 00:38:43 Re: no space left on device
Previous Message Martijn van Oosterhout 2004-01-10 00:20:11 Re: ERROR: Cannot insert a duplicate key into unique index pg_class_relname_nsp_index