On Monday 19 March 2018 20:40:00 Nick Koretsky wrote: > > > Well, i mean does reboot reclaim that lost space? You see one of a > > > possible reason for a "vanished" space are open deleted files. If some > > > daemon misbehave with cache or imporper log rotations, etc... > > > > It does reclaim some of the lost space, yes - hence one reason for > > rebooting, when I run out of space - but there is still a creeping issue > > of space disappearing in increments of a couple mb at a time. > > Well, than you have two different issues at hand. Two deal with a space > that is reclaimed by reboot, run (when some space already gone) > lsof -nP +L1 > and look for anything suspicious here. All entries are marked as deleted. I could give you the whole list, but it is very long, and besides I am trying not to give out my user name, and other specific details. Anything I ought to look for, if all items are already marked as deleted? > Also, if /tmp is on real disk (not > tmpfs), it is also a primal suspect for a space that is reclaimed by > reboot. > I did look in /tmp, but there is nothing much there; although the presence of a systemd entry does bother me - but maybe this is by design. > For an issue with a long term lost space, the only thing i cab suggest it > to setup a cron to run something like > du -xcbd2 / > $(date +\%j%H) Running the cron job now. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
