Ken Irving wrote:
On Wed, Nov 15, 2006 at 08:54:15PM +0000, J.A. de Vries wrote:
On 2006-11-15 @ 11:20:46 (week 46) Ralph Katz wrote:
How about:
# rm -f 1141914051.*
No promises... but something like that worked once for me in a similar
mysterious situation.
Ah, hadn't tried that yet. Too bad it didn't work.
$ rm -i 1141914051.*
rm: cannot lstat
`1141914051.M484859P8695V0000000000000309Ip0007553_0.draupnir,S=3707:2,S':
No such file or directory
The file doesn't exist.
See if find sees the file, e.g.,
find -name 11419\*
Since it doesn't exist, "find" cannot find it, either.
OTOH, something is there. Try using
# lsof
He probably has a file which has been deleted, but which
some process still has open. This causes the directory
entry to be marked "for deletion", but for the allocation
not to be released to free space until the last process
has closed the file.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
