| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Palle Girgensohn <girgen(at)FreeBSD(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Julian Akehurst <julian(at)pingpong(dot)net> |
| Subject: | Re: leaking lots of unreferenced inodes (pg_xlog files?), maybe after moving tables and indexes to tablespace on different volume |
| Date: | 2013-03-13 02:03:56 |
| Message-ID: | 10115.1363140236@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Palle Girgensohn <girgen(at)FreeBSD(dot)org> writes:
> ... I got lots of space freed
> up, but it seems that after that the disk usage grows linearly (it seems
> to leave many inodes unreferenced).
Hm. We've seen issues in the past with PG processes failing to close
no-longer-useful files promptly, but ...
> Strange thing is I cannot find any open files.
... that suggests there's something else going on.
> The unreferenced inodes are almost exclusively around 16 MB in size, so
> i.e. they would most probably all be pg_xlog files.
Have you got any sort of WAL archiving active, and if so maybe that's
holding onto WAL files? Not that it's clear how come lsof wouldn't
tattle on an archiving process either.
> Stopping postgresql briefly did not help, I tried that.
That seems to point the finger at some non-postgres cause. I confess
I can't guess what.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-03-13 03:14:02 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Previous Message | Palle Girgensohn | 2013-03-13 00:37:13 | leaking lots of unreferenced inodes (pg_xlog files?), maybe after moving tables and indexes to tablespace on different volume |