From owner-freebsd-stable Sun Aug 8 15:24:14 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 9C52E14C2E for ; Sun, 8 Aug 1999 15:24:03 -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 PAA00291; Sun, 8 Aug 1999 15:22:25 -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 15:22:24 -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 Tom, thanks for the suggestion to use clri and fsck. This did the trick! David, I have Seagate SCSI drives, so it's not the IDE problem you described. My conclusion is that there is something not right in the kernel if trying to remove a file causes it to panic. Remove should be a lot like what clri and fsck does -- dellocate the inode, update free block map, tie up any loose ends so that that filesystem is stable. Apparently, rm is trying to do more -- perhaps stat the file in some way that is getting tripped up on odd characteristics of the file entry (since it looks like a block or character device, etc.). Since these odd files are not supposed to show up at all, I presume the kernel is assuming that such a situation never occurs and doesn't have to plan for that contingency. --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message