OSX Leopard: Trash Always Full
Guess I am getting closer to running a well-usable version of Leopard, but I am not quite there yet: Since yesterday, my Trash turns out to be always shown as “full”:
(Yes, Papierkorb is the German word for “paper bin”).
So far, I haven’t been able to figure out why this happens — there’s nothing in there, really. I even “sudo rm -rf“-deleted the .Trash folder out of my home folder, but it didn’t help. OSX did automatically recreate it (empty!) but the dock icon won’t change.
For now, I guess I’ll have to live with an “overflowing” trash can — if you have any hints though what else I could do, a comment would be very much appreciated 
Update: It’s fixed! It was a filesystem corruption in the fat32 filesystem. I ran a chkdsk which converted the “undeletable” file into one that I was able to remove. Thanks for pointing me into the right direction, Jean Pierre and Greg!
Do you have any external drives connected? Did you check their
.Trashfolders?Hm! Maybe my bootcamp partition has one and for some obscure reason it’s broken? Lemme look
chronos:/Volumes/WINDOWS fred$ sudo rm -rf .Trashes ._.T*
Password:
rm: .Trashes/501/\004␀␀␀õ\001␀␀.õ\001␀: File name too long
rm: .Trashes/501: Directory not empty
rm: .Trashes: Directory not empty
–> ah-hah! Looks like I need to do a filesystem check on the windows partition.
Is there any file system (FAT) corruption?
Indeed, thanks! I ran a chkdsk and after that, I was able to remove a (strange) file off the Trash on the Bootcamp partition.
Hi,
I had the exact same issue with the exact same strange filename.
The disk repair solved it for me too (The 501 folder had been changed into a file).
I should just make clearer than the repair must be done running windows. The Apple “Disk Utility” doesn’t help.
Im having the same problem, I have the following file in my trash running Leopard 10.5.2:
␀␀␀õ␀␀.õ␀ 0k Alias
I ran a chkdsk on my FAT32 windows partition thru XP and it found errors, but did not allow me to fix the problem back on the MAC side. Any advise?
I had the same problem of Ari (comment 7) fixed erasing the fat32 partition…
thanks!