From owner-freebsd-current  Sat Apr  6 06:59:22 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA02003
          for current-outgoing; Sat, 6 Apr 1996 06:59:22 -0800 (PST)
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA01998
          for <current@freefall.freebsd.org>; Sat, 6 Apr 1996 06:59:20 -0800 (PST)
Received: by pcnet1.pcnet.com (4.1/SMI-4.1)
	id AA06406; Sat, 6 Apr 96 09:56:27 EST
Date: Sat, 6 Apr 96 09:56:27 EST
From: eischen@vigrid.com (Daniel Eischen)
Message-Id: <9604061456.AA06406@pcnet1.pcnet.com>
To: freebsd@hopf.math.purdue.edu, msmith@atrad.adelaide.edu.au
Subject: Re: Clean reboot on current
Cc: current@freefall.freebsd.org, wilker@hopf.math.purdue.edu
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Clarence Wilkerson stands accused of saying:
> > When I do a few syncs and a "reboot" command, I get a string of
> > numbers like
> > 
> > 3 3 3 3 3 3   "giving up"
>
> The '3' indicates the number of disk buffers that are waiting to be
> written.    Do you get the same result with 'shutdown -r now'?
> If not, then you probably have an application that's unhappy about being
> nuked.

Like a Linux partition that is still mounted at reboot time?  That's what
I get if I fail to umount the Linux partition before rebooting.  Booting
Linux (eek! I hate to admit it) then requires a file system check.

Dan Eischen
eischen@pcnet.com