From owner-freebsd-current Sat Sep 9 9: 6:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id F2FED37B423; Sat, 9 Sep 2000 09:06:54 -0700 (PDT) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.0/8.11.0) with ESMTP id e89G6rg93669; Sat, 9 Sep 2000 09:06:53 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <5.0.0.19.2.20000909090502.00a74d98@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.19 (Beta) Date: Sat, 09 Sep 2000 09:06:53 -0700 To: Robert Watson , John Baldwin From: Manfred Antar Subject: Re: Dirty buffers on reboot.. Cc: current@FreeBSD.ORG In-Reply-To: References: <200009081942.MAA57127@pike.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:59 AM 9/9/2000 -0400, Robert Watson wrote: >On Fri, 8 Sep 2000, John Baldwin wrote: > >> Ok, an update on the dirty buffers on reboot: >> >> If you use the reboot command, you will get dirty buffers. If you use >> 'shutdown -r now' instead, you won't get dirty buffers. Thus, as a >> workaround for now, use the shutdown command to reboot your box until we >> can track this down. > >Um. Nope. :-) I only use shutdown -r now, and I still get dirty >buffers. I too only use "shutdown -r now" and still get dirty buffers. Tor Egge posted a patch and with the patch to kern_shutdown.c I no longer have the problem. Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message