Date: Fri, 15 Jul 2005 22:11:02 +0200 From: Matthias Buelow <mkb@incubus.de> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-stable@freebsd.org Subject: Re: dangerous situation with shutdown process Message-ID: <20050715201102.GC1374@drjekyll.mkbuelow.net> In-Reply-To: <42D80E9C.70607@mac.com> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> <20050715185413.GI37261@funkthat.com> <20050715191412.GA1374@drjekyll.mkbuelow.net> <42D80E9C.70607@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Swiger wrote: >If "sysctl hw.ata.wc=0" doesn't do what you want, please submit a PR >containing something better. Or buy SCSI hardware and a real, Well, if I had the time, I would. Also if instead of softupdates, a proper journalled filesystem implementation with kernel support for write barriers in the block drivers had been implemented, we wouldn't have this problem now. Ok, no point in arguing how things would be if one had made different decisions in the past. >battery-backed up RAID system, or fibre-channel, or Firewire, or whatever >floats your boat. I would think that a significant part of (FreeBSD-) users are running FreeBSD on desktop PCs, notebooks, etc., where a fibre-channel or SCSI solution isn't really feasible (either technically, or economically). mkb.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050715201102.GC1374>