From owner-cvs-all Tue Dec 7 23:17:55 1999 Delivered-To: cvs-all@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 24F4F154D2; Tue, 7 Dec 1999 23:17:50 -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 XAA24591; Tue, 7 Dec 1999 23:19:15 -0800 Date: Tue, 7 Dec 1999 23:19:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: Nick Hibma , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_shutdown.c In-Reply-To: <199912080655.WAA01591@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > > > We are using a shutdown hook (dashutdown) as well as daclose/dadump to > > > > issue a SYNCHRONIZE CACHE to the drives. > > > > > > ... which is not supported by some drives, notably by the USB Zip drive > > > and possibly other Zip drives as well. > > > > Then they shouldn't be root filesystems, no? > > That's not really a practical way to look at it. 8) Yes, it is in fact. If you cannot guarantee data integrity, you shouldn't be running on it. If you have to run on it, don't expect data integrity. (okay, so it's a couple of buffers at shutdown- in any case, perhaps the driver that sees Synchronize Cache not working should do something else- maybe calculate the Pareto for the first occurence of a y3k bug) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message