From owner-freebsd-current@FreeBSD.ORG Fri Mar 28 16:29:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 362E937B401 for ; Fri, 28 Mar 2003 16:29:37 -0800 (PST) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8368443FE0 for ; Fri, 28 Mar 2003 16:29:36 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP id MUA74016; Fri, 28 Mar 2003 16:29:35 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C900169; Fri, 28 Mar 2003 16:29:34 -0800 (PST) To: Kevin Oberman , current@FreeBSD.ORG In-Reply-To: Message from David Schultz <20030329001859.GA22238@HAL9000.homeunix.com> Date: Fri, 28 Mar 2003 16:29:32 -0800 From: "Kevin Oberman" Message-Id: <20030329002935.C900169@ptavv.es.net> Subject: Re: Unclean sync in current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2003 00:29:38 -0000 > Date: Fri, 28 Mar 2003 16:18:59 -0800 > From: David Schultz > > Thus spake Kevin Oberman : > > I've been seeing this for a couple of weeks since I updated my laptop to > > CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown > > looked normal, with no problems reported with the sync, but, when the > > system is rebooted, the partitions are all shown as possibly > > unclean. From my dmesg: > > Mounting root from ufs:/dev/ad0s3a > > WARNING: / was not properly dismounted > > WARNING: / was not properly dismounted > > WARNING: /tmp was not properly dismounted > > WARNING: /usr was not properly dismounted > > WARNING: /var was not properly dismounted > > > > All disks are mounted with soft-updates enabled. > > > > I don't see any other reports of this. Is this unique to my system? > > Unlike the SCSI driver, the ATA driver does not send a flush cache > command to your disks before powering off the system. The kernel > waits for five seconds in either case, but for some disks that may > not be sufficient. > > The following patch should fix that, although it may have rotted a > bit in the last two months given Soeren's sweeping ATA changes. I > also edited an unrelated change out of the diff, which might > confuse patch(1). If you run into problems getting it to apply, > let me know and I'll fix it when I'm back from vacation. Thanks, but the issue was not a write cache problem. It was the change in the UFS1 super-block in V5. After I performed an fsck_ffs on each partition, the errors vanished. All appears to be running fine. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634