From owner-freebsd-stable Wed May 27 13:11:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17305 for freebsd-stable-outgoing; Wed, 27 May 1998 13:11:57 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17260 for ; Wed, 27 May 1998 13:11:30 -0700 (PDT) (envelope-from kline@tera.tera.com) Received: from athena.tera.com (athena.tera.com [207.224.230.127]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id MAA27050; Wed, 27 May 1998 12:03:47 -0700 (PDT) From: Gary Kline Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id MAA27071; Wed, 27 May 1998 12:03:46 -0700 (PDT) Message-Id: <199805271903.MAA27071@athena.tera.com> Subject: Re: improper shutdown In-Reply-To: <199805261952.MAA00933@dingo.cdrom.com> from Mike Smith at "May 26, 98 12:52:47 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 27 May 1998 12:03:45 -0700 (PDT) Cc: kemiller@hcs.harvard.edu, mike@smith.net.au, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL23 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk According to Mike Smith: > > On Monday, 05/25/98 at 11:57:35 PM, Mike Smith wrote: > > > > > > > > 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. > > > > > > Are you seeing a diagnostic at boot time telling you to update > > > /etc/fstab? Have you done so? > > > > if you're referring to the sd0a vs sd03a thing, that's not it. the only > > diagnostic i'm getting is CLEAN BIT NOT SET IN SUPERBLOCK. if you're > > referring to anything else, i don't think i've seen it. > > Sorry then, no ideas. I'm not seeing it on any systems here. I had similar problems with my 10GB 2.2.5 6x86 box. The solution was to write a simple script which fsck'd my three SCSI drives twice; then called shutdown. It's been .LT. a week since I've upgraded to 2.2.6 but so far I haven't seen the same problem. If I didn't know better, I'd guess it was a problem with the ordering of /filesystems in fstab. But what was usually ``UNCLEAN'' was /home. So... Hoping that it was one of those mysterious bugs. gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message