From owner-freebsd-stable Tue Mar 13 10:39: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 0AA7337B719; Tue, 13 Mar 2001 10:39:00 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f2DIcas00336; Tue, 13 Mar 2001 10:38:36 -0800 (PST) Message-Id: <200103131838.f2DIcas00336@ptavv.es.net> To: "Justin T. Gibbs" Cc: Alfred Perlstein , stable@freebsd.org, Soren Schmidt , scsi@freebsd.org Subject: Re: Disk I/O problem in 4.3-BETA In-reply-to: Your message of "Mon, 12 Mar 2001 15:23:22 MST." <200103122223.f2CMNMs39959@aslan.scsiguy.com> Date: Tue, 13 Mar 2001 10:38:36 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to everyone. I had no idea what an interesting thread I was spawning with my original question. Since I now understand just how dangerous running BOTH WC and SOFTUPDATES can be, I have rebuilt my kernel with WC disabled and, for a reasonably fast backup, where WC is not a data integrity issue, I have a special kernel with WC enabled. I'll just live with the slow-down in things unless smarter folks figure a way to make write cache work safely. Sometimes speed is not everything. When I brought up my first FreeBSD system I had a bad memory card which caused several crashes and hopelessly corrupted my disk. This was no big thing as I had a virgin install and it was easy to just re-install after replacing the bad RAM. But I'd find that to be a real pain today. (And I DO have a good backup today.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message