From owner-freebsd-bugs  Tue Jun  2 13:32:53 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA05169
          for freebsd-bugs-outgoing; Tue, 2 Jun 1998 13:32:53 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05125;
          Tue, 2 Jun 1998 13:32:27 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA26080;
	Wed, 3 Jun 1998 06:32:22 +1000
Date: Wed, 3 Jun 1998 06:32:22 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199806022032.GAA26080@godzilla.zeta.org.au>
To: freebsd-bugs@FreeBSD.ORG, grog@lemis.com, phk@FreeBSD.ORG
Subject: Re: bin/6794
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>Synopsis: Cannot remount root file system after fsck
>
>State-Changed-From-To: open-closed
>State-Changed-By: phk
>State-Changed-When: Tue Jun 2 04:09:21 PDT 1998
>State-Changed-Why: 
>cannot reproduce on -current

It's easy to reproduce.  Put an alias for the device containing the root
file system in /etc/fstab and crash.  Then fsck won't know that the raw
device that it works on is for the root file system and the root file
system won't be reloaded.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message