From owner-freebsd-current Sat Apr 11 18:39:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19691 for freebsd-current-outgoing; Sat, 11 Apr 1998 18:39:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19676 for ; Sat, 11 Apr 1998 18:39:52 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA02518; Sat, 11 Apr 1998 20:39:44 -0500 (EST) (envelope-from toor) Message-Id: <199804120139.UAA02518@dyson.iquest.net> Subject: Re: disk damage In-Reply-To: from Chuck Robey at "Apr 11, 98 06:26:34 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Sat, 11 Apr 1998 20:39:44 -0500 (EST) Cc: FreeBSD-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey said: > > rm: usr/src/usr.bin: Bad file descriptor > rm: usr/src/usr.sbin: Bad file descriptor > [extra error list, about 8, removed] > > I tried to do an ls of those directories, and got: > > ls: usr.bin: Bad file descriptor > ls: usr.sbin: Bad file descriptor > > Should I continue to delete these guys, and if so, how? > Try doing fsck after the attempted rm commands. Make sure that you reboot with -s, before the additional fsck commands. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message