The title says it (I mean, when a new file is created in an other application). This started happening today, and I think this may be related to an error message which I got the first time in yesterday evening:
This is the link from screenshot: https://openradar.appspot.com/radar?id=1387401 — just in case you want to check it out. And, of course, I did a reboot after that message.
The issue is not reproduced in 100% of the trials, but it's there…
I checked the disk with Disk Utility and it says it's OK.
What could it be?
Analysis
The output of df -ki
:
Filesystem 1024-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1 487385240 443717640 43411600 92% 110993408 10852900 91% /
devfs 202 202 0 100% 703 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net
map auto_home 0 0 0 100% 0 0 100% /home
After deleting some trash:
Filesystem 1024-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1 487385240 391070420 96058820 81% 97831603 24014705 80% /
devfs 201 201 0 100% 698 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net
map auto_home 0 0 0 100% 0 0 100% /home
df -ki
. – dan Apr 17 '15 at 7:13