In article <1g51a4a.zjra1316aasw0N%net>, net
I assume you've tried 'rm -rf *' too. Sounds like you have a fux0red
Have you tried deleting by inode? I'm not going to test this on my box
and I would wait for someone who knows more than I do to say whether
this is insane or safe before trying but here's a suggestion:
Get the dodgy file's inode:
ls -i file_i_cant_delete
Will give output something like:
That gives you the inode of the file - 10607690 in this case.
Use 'df' to find the name of the device the file lives on:
Find your troublesome volume - the numbers and diskX_X bit will be
different but you're looking for a line like:
/dev/disk0s4 138567440 86208 138481232 0% /Volumes/Datenschleuder
It's all been safe up to here - I'm not sure on the next bit so take
clri /dev/disk0s4 10607690
Using the /dev/diskXsX and inode number obtained previously...
Now run 'fsck' on the volume...
To be honest though if the filesystem is shagged I would rather backup,
reformat and restore - and use HFS+ (Journaled).
Good luck :/