>
> which, of course, truncated the file to 0 bytes and i was able to delete it.
> right now / is at 1.4GB, meaning that file must have been somewhere around
> 5GB. i must have screwed up royally on that find command. i don't see
> anything wrong with it; i must have retyped it.
>
> anyway, that was my first experience with a file that was too large. it was
> interesting.
>
> peter
Pete - the only thing I could think of that could cause
something like this is if find were following a symlink
and recursing over the same files over and over while
you washed =)
Micah
