Hi Sthu, Am Montag, 20. Mai 2013, 12:06:11 schrieb Sthu Deus: > Good time of the day. > > > I watch carefully disk space on my root device i try to find the > culprit that fills the space. > > For example, i have free space only 100 MiB. After 2-3 hours space is > gone. After reboot i see the space again. > > What i did is "du -ms" for every dir. on the disk only (not > for /dev, /sys, ...) - before i have the space and after it vanished > away. > > The interesting point is that though total free disk spaces are > different for the amount of MiB, yet every dir. size is the same or 2-3 > of it differs no more that 1 MiB. > > So question is, how it may be? Is it so large calculations drift ?
btrace /dev/dm-0 on an otherwise idle system might help. If system is not idle otherwise you likely get too much output. blktrace needs to be installed for this. I think I remember some knob in /proc or /sys which has a similar effect and you can watch I/O accesses in dmesg then, but I didn´t find it right now. Otherwise I like the suggestion to watch with iotop. You can run iotop in batch mode and output stuff to a file to inspect later (but be careful about free space on / :). I´d strongly suggest more than 100 MiB free space on /. Usually its good to leave at least 10-20% of the filesystem free to avoid fragmentation. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/4545470.3iDn6scfhm@merkaba
