From owner-freebsd-stable Sun Aug 8 14:51:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.cts.com (io.cts.com [198.68.174.34]) by hub.freebsd.org (Postfix) with ESMTP id 1370415044 for ; Sun, 8 Aug 1999 14:51:13 -0700 (PDT) (envelope-from mdavis@cts.com) Received: from VOYAGER (voyager.cts.com [198.68.174.38]) by io.cts.com (8.9.3/8.9.2) with SMTP id OAA01256; Sun, 8 Aug 1999 14:49:21 -0700 (PDT) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: "Tom" , "David Malone" Cc: Subject: RE: Removing files in /lost+found causes panic Date: Sun, 8 Aug 1999 14:49:21 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2918.2701 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't think you should ever need to use clri. The system should only > panic if the filesystem is corrupt. If fsck finds serious damage, you > should run it again to make sure everything. Chances are the first fsck > left some unfixed problems. > > Tom Tom, fsck has been run several times (multiples in single user mode, with syncs in between, and across several reboots), and shows no problems at all. Yet, any attempt to molest the files in /lost+found initiates an immediate panic. I think the clri method might be the best way, and I'll try that next. SCO has an unlink command that sounds like it does the same thing, only you pass it a file or directory name. Just takes it out and the next fsck cleans up after you. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message