From owner-freebsd-current Tue Dec 7 8:19: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2D17D14D31 for ; Tue, 7 Dec 1999 08:19:02 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA21823; Tue, 7 Dec 1999 08:20:15 -0800 Date: Tue, 7 Dec 1999 08:20:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Luoqi Chen Cc: jazepeda@pacbell.net, phk@critter.freebsd.dk, brian@CSUA.Berkeley.EDU, current@FreeBSD.ORG, vallo@matti.ee Subject: Re: mount(2) broken? In-Reply-To: <199912070716.CAA16646@lor.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Dec 1999, Luoqi Chen wrote: > > I've seen this exact same thing before too. In fact it was two rather > > annoying things, one being a single solitary last buffer that wouldn't > > sync and thus left the whole fs marked dirty, and then fsck would check > > it, see it was fine, but mount wouldn't recognize that it was clean. > > > > 'Course I saw this this morning too. Yes, with a new kernel, new devices, > > ata driver, and new world. 'Twas very odd. > > > > - alex > > > I'd like to add something about the last buffer wouldn't sync. This occurs > when a shutdown syscall is issued when the syncer process is asleep waiting > for a buffer write to complete. The write will never complete, because the > syncer won't be given a chance to run again, and the buffer will stay marked > as busy and become the buffer that wouldn't sync. I haven't thought about > a clean way of handling this situation, maybe some of you out there have > better ideas... Ah. That *could* be happening to me, but this happens even with a quiescent system (I mean, several times with nothing happening). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message