ok, part of my problem is not understancing how much linux lies to me.

after a reboot, it does show 95% full.

but doing the math on the blocks used/total,

it is technically under 90% full, and what it tells me is "available" is 5%, so the difference is being withheld from me. unless those numbers are innacurate or there is some basic issue I don't understand.

I don't know enough of the internal workings to know if that is reasonable, or a holdover from when disks were smaller.

if it is more than reasonable, the problem is that I could get to ignore the "disk almost full" warnings even when it really is almost full.

Carey

On 08/25/2025 10:22 AM CDT Alvin Starr via Talk <talk@lists.gtalug.org> wrote:

On 8/25/25 11:08 AM, CAREY SCHUG via Talk wrote:

I'm guessing somebody will tell me I have to reboot, but why did none of the instructions on the internet say that? and since I was allowed to delete all the snaps that should imply none were in use, so why would a reboot be needed?

A common thing that can bite you is the unix feature that if a file is open and you delete the file it will not be removed from the filesystem until the program with the file open closes it or exits (closing all the open files).

This usually gets people trying to remove log files but not restarting the service that has the logfile open.

If you know the file or directory you could likely use lsof to track down the program that has the open file.
-- 
Alvin Starr                   ||   land:  (905)513-7688
Netvel Inc.                   ||   Cell:  (416)806-0133
alvin@netvel.net              ||
------------------------------------
Description: GTALUG Talk
Unsubscribe via Talk-unsubscribe@lists.gtalug.org
Start a new thread: talk@lists.gtalug.org
This message archived at https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/ITZJCZJHTEBPFSORXOL5FIWXCQPMH2T6/