From owner-freebsd-questions Tue Jul 23 16:01:25 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA22088 for questions-outgoing; Tue, 23 Jul 1996 16:01:25 -0700 (PDT) Received: from jbrann.dialup.access.net (jbrann.dialup.access.net [166.84.193.118]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA22080 for ; Tue, 23 Jul 1996 16:01:21 -0700 (PDT) Received: (from jbrann@localhost) by jbrann.dialup.access.net (8.7.5/8.7.3) id SAA26607 for questions@freebsd.org; Tue, 23 Jul 1996 18:40:42 -0400 (EDT) Message-Id: <199607232240.SAA26607@jbrann.dialup.access.net> Subject: Disk corruption after crash on Toshiba laptop To: questions@freebsd.org (freeq) Date: Tue, 23 Jul 1996 18:40:41 -0400 (EDT) Reply-To: byron@netapp.com From: John Brann Reply-To: John Brann Organisation: Not while I'm at home X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Major corruption: about 50-60 inodes got lost and relinked into lost+found. The man command no longer works because some piece of groff is missing. This is after a perfectly ordinary crash. UFS has strict ordering rules fo writing data to disk which I am afraid freebsd might be violating. I expect a fsck after a dirty halt, but I don't expect the fsck to fail!