Date: Tue, 07 Dec 1999 23:26:27 -0800 From: Mike Smith <msmith@freebsd.org> To: mjacob@feral.com Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_shutdown.c Message-ID: <199912080726.XAA04037@mass.cdrom.com> In-Reply-To: Your message of "Tue, 07 Dec 1999 23:19:15 PST." <Pine.BSF.4.10.9912072317040.35786-100000@beppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > 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. I thought your argument was "we ought to work properly where it's possible, rather than pursue some golden ideal of perfection"? > (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) You could just delay for a couple of seconds and guarantee that even if the Synchronise Cache command didn't work, the drive will still have flushed it's cache. Oops, looks like that's what I committed the other day. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912080726.XAA04037>