From owner-freebsd-stable Mon May 25 20:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07763 for freebsd-stable-outgoing; Mon, 25 May 1998 20:31:31 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hcs.harvard.edu (hcs.harvard.edu [140.247.73.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07754 for ; Mon, 25 May 1998 20:31:24 -0700 (PDT) (envelope-from kemiller@hcs.harvard.edu) Received: (from kemiller@localhost) by hcs.harvard.edu (8.8.5/8.8.3) id XAA30001; Mon, 25 May 1998 23:31:16 -0400 (EDT) Message-ID: <19980525233116.10709@hcs.harvard.edu> Date: Mon, 25 May 1998 23:31:16 -0400 From: Kenneth Miller To: freebsd-stable@FreeBSD.ORG Subject: improper shutdown Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk I've had a minor (?) but irritating problem ever since moving to stable from 2.2.5. When I reboot, the disks don't have their clean flags set and need fscking. If I shutdown to singer user mode and manually unmount the disks, and remount / readonly, it's fine. But using the shutdown program to go all the way doesn't work. I will assume this is some misconfiguration on my part, but I was a little perplexed that it began only when I moved to stable. Any suggestions or answers appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message