sysutils/dolly breaks cvs

Aryeh Friedman aryeh.friedman at gmail.com
Fri Mar 11 17:52:05 UTC 2011


On Fri, Mar 11, 2011 at 12:11 PM, Wesley Shields <wxs at freebsd.org> wrote:
> On Fri, Mar 11, 2011 at 11:35:02AM -0500, Aryeh Friedman wrote:
>> This is from a repo that was updated 15 mins ago:
>>
>> flosoft-stable# cvs co ports/sysutils/dolly |& more
>> cvs checkout: Updating ports/sysutils/dolly
>> cvs checkout: Updating ports/sysutils/dolly/files
>> cvs checkout: Updating ports/sysutils/dolly/files/
>> cvs checkout: Updating ports/sysutils/dolly/files//
>> cvs checkout: Updating ports/sysutils/dolly/files///
>> cvs checkout: Updating ports/sysutils/dolly/files////
>> cvs checkout: Updating ports/sysutils/dolly/files/////
>
> Please don't top-post.
>
> You have something weird going on. There has not been a commit there in
> years. This is most likely a local problem. Can you find a way to force
> your repo to update that again?

Ok this now truely weird I have a infinite recursive directory rooted
on /home/ncvs/ports/sysutils/dolly/files that contains one dir per
level whose name is a single control-N when I try to rm/unlink them I
get:

flosoft-stable# pwd
/repo/ports/sysutils/dolly/files
flosoft-stable# rm -rf *
rm: /: Operation not permitted
rm: : Invalid argument

If I know the inode how can I force the inode to be cleared even if
the filename is illegal?


More information about the freebsd-ports mailing list