From owner-freebsd-questions@FreeBSD.ORG Thu Jul 14 22:09:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DB3516A41C for ; Thu, 14 Jul 2005 22:09:11 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0900543D49 for ; Thu, 14 Jul 2005 22:09:09 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 3091 invoked from network); 14 Jul 2005 22:09:09 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Jul 2005 22:09:09 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 30A0442; Thu, 14 Jul 2005 18:09:08 -0400 (EDT) Sender: lowell@be-well.ilk.org To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714195253.GA23666@drjekyll.mkbuelow.net> From: Lowell Gilbert Date: 14 Jul 2005 18:09:07 -0400 In-Reply-To: Message-ID: <447jftrqf0.fsf@be-well.ilk.org> Lines: 34 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: dangerous situation with shutdown process X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 22:09:11 -0000 Jon Dama writes: > softupdates is perfectly safe with SCSI. > > its well known that ide and sata w/wo ncq fails to provide suitable > semantics for softupdates > > however, journaling fairs no better, and request barriers do nothing to > solve the problem. I had assumed that the sequence of operations in a journal would be idempotent. Is that a reasonable design criterion? [If it is, then it would make up for the fact that you can't build a reliable transaction gate. That is, you would just have to go back far enough that you *know* all of the needed journal is within the range you will replay. But even then, the journal would need to be on a separate medium, one that doesn't have the "lying to you about transaction completion" problem.] > On Thu, 14 Jul 2005, Matthias Buelow wrote: > > > Kevin Oberman wrote: > > > > >SCSI or ATA? If it's ATA, turn off write cache with (atacontrol(8) or > > >the sysctl. > > > > You do NOT want to do that. Not only will performance drop brutally > > (example: drop to 1/5th of normal write speed for sequential writes, > > probably worse for random writes) but it will also significantly > > reduce the lifetime of your disk. Modern disks are designed to be > > used with the write-back cache enabled, so don't turn it off. I have no idea what "designed to be used with the write-back cache enabled" could affect the operating life of the disk.