"Leaking" disk space
godders at gmail.com
Thu Mar 21 10:40:49 UTC 2013
> Have you used fstat to identify the big growing file which is taking up the space, and which process has the file open?
It's not an unlinked file. I've tried using fstat and lsof to identify
it, and there's no inodes with zero links or that don't have a
matching file on disk.
On 20 March 2013 23:08, Daniel O'Callaghan <danny at clari.net.au> wrote:
> On 21/03/2013 3:55 AM, Dan Thomas wrote:
>> Stopping Postgres doesn't fix it, but rebooting does which points at
> Have you used fstat to identify the big growing file which is taking up the
> space, and which process has the file open?
> A file which has been unlinked from all directories won't be seen by du, but
> it does not free disk space until no process has it open.
> USER CMD PID FD MOUNT INUM MODE SZ|DV R/W
> root syslogd 47648 8 / 4317027 -rw-r--r-- 19776 w
> root syslogd 47648 9 / 4317041 -rw------- 63 w
> That might help to track it down.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions