Good time of the day, Martin.
Thank You, Martin, for Your time and answer. You wrote: > btrace /dev/dm-0 > > on an otherwise idle system might help. If system is not idle > otherwise you likely get too much output. At random, I have found who ate the space( or one among others) - I just catched it! :o) > 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. I will try it if there will be such need. > 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 / :). Oh! I even did not guess it has such ability! Thank You! > 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. And that makes 10-20% extra money spending on HDD purchase. :o) Sthu. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/519e4ba2.6d0cb40a.4323.ffffa...@mx.google.com
