From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs un-removable file
In-Reply-To: Your message of "Mon, 27 Oct 2003 13:07:01."
             <282c78e6ec6bc78ab2d7cad2c2466c62@yourdomain.dom>
From: "Russ Cox" <rsc@swtch.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <63019.1067261701.1@t40.swtch.com>
Message-Id: <E1AE7WQ-000GOT-5t@t40.swtch.com>
Date: Mon, 27 Oct 2003 08:35:01 -0500
Topicbox-Message-UUID: 79dea410-eacc-11e9-9e20-41e7f4b1d025

> Maybe I should just ignore this but I have managed to
> create a file that I cannot remove (under kfs).
>
> I have tried
> 	disk/kfscmd 'remove /usr/steve/work/pcp/e=C2=80=C2=80B'
> and=
> 	disk/kfscmd 'clri /usr/steve/work/pcp/e=C2=80=C2=80B'
> but both of them error with "can't walk e=C2=80=C2=80B"
>
> NB the above where cut and paste so the runes are correct.

I doubt that.  C2 80 is UTF for 0x80, the error rune.
When any of the UTF routines process a bad UTF sequence, they
replace it with the error rune.  So what's really happening,
probably, is that kfs is giving you bad data (not UTF) and
ls is coping.

If you write a program to walk through the directory manually
and call remove on the offending file, you should be fine.
Just avoid all the utf routines (like print!).

Of course, kfs might check that names you give it are okay
UTF, but off the top of my head I don't think it does.

Russ