Nejc Škoberne ?:
Hey,
My guess is that something has mmap-ed a HUGE chunk of
disk space. If I reboot the space is freed.
Much more likely is that some program has deleted a large file, while
still holding it open. Usual suspect is some kind of log file,
or temporary file.
Then I just
Artem Kuchin wrote:
Unfortunatelly no, it does not. I don't have md at all, but reboot
always solves the problem and i still have
no idea how to look at what's eating the disk space.
fstat shows all (amongst other things) open files (actually inode numbers)
Peter
--
Hello!
Look at this:
/dev/da0s1f 104164493 104061031 -8229697 109%/usr
but
du -k -d1 /usr
gives a lot less (about 20GB).
My guess is that something has mmap-ed a HUGE chunk of
disk space. If I reboot the space is freed.
The question is how can i sees what process mmaped how much
space
On Mon, Jun 23, 2008 at 03:45:37PM +0400, Artem Kuchin wrote:
Hello!
Look at this:
/dev/da0s1f 104164493 104061031 -8229697 109%/usr
but
du -k -d1 /usr
gives a lot less (about 20GB).
My guess is that something has mmap-ed a HUGE chunk of
disk space. If I reboot the space is
Hey,
My guess is that something has mmap-ed a HUGE chunk of
disk space. If I reboot the space is freed.
Much more likely is that some program has deleted a large file,
while still holding it open. Usual suspect is some kind of log file,
or temporary file.
I also had a similar problem,
