On Fri, Aug 15, 2025 at 11:38:54AM -0400, R. Clayton wrote: > This is the first occurrence of an error for sd0a. sd0a is reported as being > full > > $ df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/sd0a 986M 941M -4.8M 101% / > /dev/sd0l 295G 6.8G 274G 3% /home > /dev/sd0m 1.4T 864G 500G 64% /mnt/nfs > /dev/sd0d 3.9G 20.0K 3.7G 1% /tmp > /dev/sd0f 29.1G 1.7G 26.0G 6% /usr > /dev/sd0g 986M 331M 605M 36% /usr/X11R6 > /dev/sd0h 19.4G 2.2G 16.2G 13% /usr/local > /dev/sd0k 5.8G 2.0K 5.5G 1% /usr/obj > /dev/sd0j 2.9G 2.0K 2.8G 1% /usr/src > /dev/sd0e 34.3G 20.3M 32.6G 1% /var > /dev/sd1d 1.4T 1014G 305G 77% /mnt/lacie/d > /dev/sd1e 456G 4.0K 433G 1% /mnt/lacie/e > > $ > > But is it? > > $ sudo du -chxd 1 / > 4.0K /home > 26.0K /mnt > 2.0K /tmp > 2.0K /usr > 2.0K /var > 2.0K /altroot > 7.1M /bin > 42.0K /dev > 53.0M /etc > 1.2M /root > 17.0M /sbin > 175M / > 175M total > > $
Files which are held open but unlinked in the filesystem will not be seen with du, but will still count as used space in the output of df. Simple reproducer: # dd if=/dev/random of=/foobar bs=1m count=128 # vi /foobar On another VT whilst vi is still open: # rm /foobar ... then compare the output of du and df before and after exiting vi.
