From owner-freebsd-questions  Tue Nov  9 23:30:51 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from spits.calcasieu.com (spits.calcasieu.com [209.99.46.70])
	by hub.freebsd.org (Postfix) with ESMTP id DD75F14BCC
	for <questions@FreeBSD.ORG>; Tue,  9 Nov 1999 23:30:43 -0800 (PST)
	(envelope-from dread@calcasieu.com)
Received: from coypu.bb.calcasieu.com (coypu.bb.calcasieu.com [192.168.3.21])
	by spits.calcasieu.com (8.9.3/8.9.3) with ESMTP id BAA34107;
	Wed, 10 Nov 1999 01:30:04 -0600 (CST)
	(envelope-from dread@calcasieu.com)
Message-ID: <XFMail.991110013004.dread@calcasieu.com>
X-Mailer: XFMail 1.3.1 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3828D31A.F44A497C@megadeth.org>
Date: Wed, 10 Nov 1999 01:30:04 -0600 (CST)
Organization: Calcasieu Lumber
From: Don Read <dread@calcasieu.com>
To: Shawn Ramsey <shawn@megadeth.org>
Subject: RE: f'ed up directory!
Cc: questions@FreeBSD.ORG
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 10-Nov-99 Shawn Ramsey wrote:
> Im not sure what happened here... here is the output if I try to rm a
> directory. I cannot get rid of it. This was in someone's home directory,
> I dunno if they actually created these dirs/files, the file system is
> somehow partly hosed, or what. But if anyone can tell me what I might be
> able to do to get rid of this, id appreciate it. Something other than
> newfs would be nice. :)
> 
> /home/jwarr {375}>rm -rf bla
> rm: bla/12916/
> YOUR PUBLIC SSH1 KEY (-b 512) GOES HERE!
> /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AA
> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AA
> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AA
> AAAAAAAAAA/

<snip>

> AAAAAAAAAA: File name too long
> rm: bla/15934/+ +
> /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AA
> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AA
> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
> AA
> AAAAAAAAAA/+ +


<snip>

> AAAAAAAAAA: Directory not empty
> rm: bla/19550/1/2/3/4/5/6/7/8/9/10/+ +
>: Directory not empty
> rm: bla/19550/1/2/3/4/5/6/7/8/9/10: Directory not empty
> rm: bla/19550/1/2/3/4/5/6/7/8/9: Directory not empty
> rm: bla/19550/1/2/3/4/5/6/7/8: Directory not empty
> rm: bla/19550/1/2/3/4/5/6/7: Directory not empty
> rm: bla/19550/1/2/3/4/5/6: Directory not empty
> rm: bla/19550/1/2/3/4/5: Directory not empty
> rm: bla/19550/1/2/3/4: Directory not empty
> rm: bla/19550/1/2/3: Directory not empty
> rm: bla/19550/1/2: Directory not empty
> rm: bla/19550/1: Directory not empty
> rm: bla/19550: Directory not empty
> rm: bla: Directory not empty
> 
> 
> 
> 


from freebsd-security:

 ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-99:05.fts.asc

-- and -


>Actually, the problem is fts(3) being broken.  Use my
>little program for
>this situation over at http://www.freebsd.org/~green/deltree.c
>
>-- 
> Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
> green@FreeBSD.org                    `------------------------------'




Regards,
---
Don Read                                           dread@calcasieu.com
EDP Manager                                            dread@texas.net
Calcasieu Lumber Co.                                         Austin TX
-- any similarity between the word and the thought is entirely coincidental


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message