From owner-freebsd-geom@FreeBSD.ORG Fri May 4 19:53:05 2007 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 135B816A46B for ; Fri, 4 May 2007 19:53:05 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30304.mail.mud.yahoo.com (web30304.mail.mud.yahoo.com [209.191.69.66]) by mx1.freebsd.org (Postfix) with SMTP id B7F0713C4B8 for ; Fri, 4 May 2007 19:53:04 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 38737 invoked by uid 60001); 4 May 2007 19:53:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=c+w2y1PZPyXFipjkSmlrvo5J3KWDp613oO4S3tmIp5h1JQj73lGxjA7Pclswz1IJKHDx1XlbuUr9LXXW0VO+abvT27mXOvs7KcMOgKedcsWKzBErBmRfzFH8vMbZr32TMgZwUxUjdwOkaJWUmDyNDzwLLRkxLJNwwBUgHV9VIIw=; X-YMail-OSG: nW4FksQVM1nMoiKMhuTtOc6Mr9IDy4z5hPJ12U7vzFYfSZveg.GBGKKi.byXksmTqACsgWG5FKfp0tXVuZJJJugpSeDBziGd5jOmxZdCpoXLLmdoYsgfzNPdKw-- Received: from [85.212.5.38] by web30304.mail.mud.yahoo.com via HTTP; Fri, 04 May 2007 12:53:04 PDT Date: Fri, 4 May 2007 12:53:04 -0700 (PDT) From: Arne "Wörner" To: deniswork In-Reply-To: <171980743.20070504223126@uzvik.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <125507.38194.qm@web30304.mail.mud.yahoo.com> Cc: freebsd-geom@freebsd.org Subject: Re: Re[2]: graid5 after-reboot problem X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2007 19:53:05 -0000 --- deniswork@uzvik.kiev.ua wrote: > than i create new array, and all goes fine. > I rebooted server few times, all was fine. > I start coping my data, than power reboot happens... > In rare cases a power failure might cause a UFS to be badly damaged, I think... This is caused by write caches (in the disks and in graid5)... U might want to run graid5 with sysctl kern.geom.raid5.wdt=0 (that disables the write cache in graid5, which slows down write requests) -Arne ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/