Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!usc!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!marob!daveh
From: daveh@marob.masa.com (Dave Hammond)
Newsgroups: comp.unix.wizards
Subject: Re: Removing garbage files
Message-ID: <266B2780.3A84@marob.masa.com>
Date: 5 Jun 90 03:31:12 GMT
References: <156@TWG.UUCP> <610@atcmpe.atcmp.nl> <13043@smoke.BRL.MIL>
Reply-To: daveh@marob.masa.com (Dave Hammond)
Organization: ESCC,  New York City
Lines: 17

In article <13043@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
>In article <610@atcmpe.atcmp.nl> ronald@atcmp.nl (Ronald Pikkert) writes:
>>Your shell probably strips the high order bit which causes rm to be unable
>>to delete these files.
>
>But that doesn't explain why "rm -r" would fail to remove them.

Is it possible that there is really no file with this weird name, but
the directory itself got bashed so that a directory slot which should
have zeros in the inode field actually contains garbage?  Wouldn't this
make ls think there was a file with a garbage name, but unlink would
fail causing rm to claim the file was not found?

--
Dave Hammond
daveh@marob.masa.com
uunet!masa.com!marob!daveh