From owner-freebsd-current@FreeBSD.ORG Wed Nov 26 11:03:28 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 388ED16A4CE for ; Wed, 26 Nov 2003 11:03:28 -0800 (PST) Received: from ptcnat.era.pl (ptcnat.era.pl [213.158.197.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D88243F85 for ; Wed, 26 Nov 2003 11:03:27 -0800 (PST) (envelope-from zaks@era.pl) Received: by localhost (Postfix, from userid 1001) id 1A5CA11426; Wed, 26 Nov 2003 20:03:26 +0100 (CET) To: "Kevin Oberman" From: =?iso-8859-2?q?S=B3awek_=AFak?= References: <20031126185136.562385D08@ptavv.es.net> Date: Wed, 26 Nov 2003 20:03:26 +0100 In-Reply-To: <20031126185136.562385D08@ptavv.es.net> (Kevin Oberman's message of "Wed, 26 Nov 2003 10:51:36 -0800") Message-ID: <86he0rymtd.fsf@thirst.unx.era.pl> User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Reasonable Discussion, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-current@freebsd.org Subject: Re: 5.2-BETA: giving up on 4 buffers (ata) 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: Wed, 26 Nov 2003 19:03:28 -0000 "Kevin Oberman" writes: >> Date: Wed, 26 Nov 2003 19:37:45 +0100 >> From: Matthias Andree >> Sender: owner-freebsd-current@freebsd.org >> >> Hi, >> >> when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on >> flushing 4 dirty blocks. >> >> I had three UFS1 softdep file systems mounted on one ATA drive, one ext2 >> file system on another ATA drive and one ext2 file system on a SCSI >> drive. Both ext2 file systems had been mounted read-only, so they can't >> have had dirty blocks. >> >> At the next reboot, FreeBSD checked all three UFS file systems as they >> hadn't been umounted cleanly before. Makes me wonder if FreeBSD gave up >> on the super blocks... > > This looks like a GEOM related issue, although I am not completely sure > of this. > > I have observed the following: > System dies leaving the file systems dirty. (File systems have > soft-updates enabled.) > I reboot to single user and fsck all partitions including the root. > I halt or reboot. > I get a number of dirty buffers and the syncer eventually gives up. > > If I issue a "mount -u /" before shutting down, the problem does not > occur. Why I should be able to get dirty buffers on a file system that > has never been mounted as RW, I don't understand, but I see it every > time I reboot after a crash. It happened to me many times on various machines. Some running 4.x, so no GEOM. I wonder why all the file systems are marked dirty. The buffers are associated with specific device anyway. /S