From owner-freebsd-questions Tue Jul 23 22:07:51 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA15321 for questions-outgoing; Tue, 23 Jul 1996 22:07:51 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts17-line7.uoregon.edu [128.223.150.224]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA15308 for ; Tue, 23 Jul 1996 22:07:47 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id WAA00322; Tue, 23 Jul 1996 22:07:41 -0700 (PDT) Date: Tue, 23 Jul 1996 22:07:41 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: byron@netapp.com, John Brann cc: freeq Subject: Re: Disk corruption after crash on Toshiba laptop In-Reply-To: <199607232240.SAA26607@jbrann.dialup.access.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 23 Jul 1996, John Brann wrote: > 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! It didn't. You haven't finished the repair: 1. Reboot to single user mode. 2. Run fsck TWICE. All lost stuff should reappear in lost+found after this is complete. 3. Copy stuff back and reboot. If it is really lost then just dump the bin distribution back on top of it. Make backups of important stuff first (like the kernel) just in case. [Crash gurus check me here.] What happened to cause the crash? Power off? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major