From owner-freebsd-questions  Tue Jul 23 22:34:36 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA17061
          for questions-outgoing; Tue, 23 Jul 1996 22:34:36 -0700 (PDT)
Received: from weaver-gw.netapp.com (weaver-gw.netapp.com [198.95.224.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA17049
          for <questions@freebsd.org>; Tue, 23 Jul 1996 22:34:34 -0700 (PDT)
Received: from netapp.com ([192.9.200.1]) by weaver.netapp.com with SMTP id <15850-14271>; Tue, 23 Jul 1996 22:34:38 +0100
Received: from bayonne.netapp.com by netapp.com (4.1/SMI-4.1)
	id AA21173; Tue, 23 Jul 96 22:34:44 PDT
Received: by bayonne.netapp.com (4.1/SMI-4.1)
	id AA29751; Tue, 23 Jul 96 22:34:42 PDT
Date: 	Tue, 23 Jul 96 22:34:42 PDT
From: byron@netapp.com (Byron Rakitzis)
Message-Id: <9607240534.AA29751@bayonne.netapp.com>
To: dwhite@resnet.uoregon.edu, jbrann@panix.com
Subject: Re: Disk corruption after crash on Toshiba laptop
Cc: questions@freebsd.org
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>It didn't.  You haven't finished the repair:

When I mean fsck failing, I mean having to resort to manual-mode fsck.

Auto-mode fsck corrects the kinds of errors you would expect from a dirty
crash on UFS. As far as I know the manual-mode fixes are fixes to the FS
for things that Can't Happen. That's why I was wondering if the disk-ordering
code was broken.

The thing that caused the crash was running ifconfig on a bad 3c589, causing
the machine to hang.