| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | "Aurangzeb M(dot) Agha" <ama-list(at)mltp(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: no space left on device |
| Date: | 2004-01-09 23:25:28 |
| Message-ID: | Pine.LNX.4.33.0401091623070.7075-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Björklund | 2004-01-09 23:30:51 | Re: no space left on device |
| Previous Message | Tom Lane | 2004-01-09 23:25:12 | Re: no space left on device |