From owner-freebsd-current  Thu Mar 13 23:07:42 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA03239
          for current-outgoing; Thu, 13 Mar 1997 23:07:42 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03230;
          Thu, 13 Mar 1997 23:07:16 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id SAA14832; Fri, 14 Mar 1997 18:01:59 +1100
Date: Fri, 14 Mar 1997 18:01:59 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703140701.SAA14832@godzilla.zeta.org.au>
To: hsu@freefall.freebsd.org, sgk@troutmask.apl.washington.edu
Subject: Re: union mounts seem to work
Cc: bde@freefall.freebsd.org, current@freefall.freebsd.org
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> Have you tried rebooting your computer single-user and manually running
>> fsck?  :-)

I don;t have thIs particular problem.

>You won't happen to be getting a "Fatal trap 12" when you reboot?
>
>root[0]: shutdown -r now
>
>gives
>
>Fatal trap 12: page fault while in kernel mode

Or this.

>The mounted filesystems are not unmounted before the trap and I get
>dropped into the debugger.  A hard reset shows all filesystems have
>some damage.

Use the panic command after getting dropped into the debugger to
minimise damage.

-current often gets recursive panics for following bad pointers in
sync() in panic() (because there are more pointers in the locking
code now).  The panic command won't reduce the damage in this case,
but it is even safer to use because it won't touch the disk at all.

Bruce