From owner-freebsd-stable Fri Feb 22 5:31:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from eve.framatome.fr (eve.framatome.fr [195.101.50.66]) by hub.freebsd.org (Postfix) with ESMTP id BBC1737B405 for ; Fri, 22 Feb 2002 05:31:18 -0800 (PST) Received: from localhost (ubc@localhost) by eve.framatome.fr (8.11.3/8.11.2) with ESMTP id g1MDUhk08620; Fri, 22 Feb 2002 14:30:43 +0100 (CET) (envelope-from ubc@eve.framatome.fr) Date: Fri, 22 Feb 2002 14:30:43 +0100 (CET) From: Claude Buisson To: Matthew Dillon Cc: Kirk McKusick , Mike Silbersack , Valentin Nechayev , "David W. Chapman Jr." , Subject: Re: Softupdates failure during buffer syncing at shutdown (was Re: cvs commit: src/sys/ufs/ffs ffs_softdep.c) In-Reply-To: <200202211908.g1LJ8UK98232@apollo.backplane.com> Message-ID: <20020222142916.O8614-100000@eve.framatome.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 21 Feb 2002, Matthew Dillon wrote: > Great! Thanks for tracking this down for us, Kirk, it would have > taken me a lot longer. > > I don't want to mess around with the sysdaemon shutdown code so what > I have done is incorporated the io_sync call into the shutdown code. > Considering the potential complexity in softupdates I wait until > normal flushing is as done as it is going to get (just in case > softupdate's sync crashes or panics) and then I call bioops.io_sync in > the remaining loop iterations. > > I have tested it and it works like a charm! I now get: > > syncing disks... 110 21 16 14 13 12 11 11 11 11 11 11 11 > done > > And, bang, on the 6th iteration after it can't sync any more it calls > io_sync and its happy. > > This will be going into -current today and -stable in three days. > Seems it had been applied to -stable, and not to -current ... Claude Buisson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message