From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 2 08:52:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CF851065670 for ; Tue, 2 Jun 2009 08:52:21 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-ew0-f164.google.com (mail-ew0-f164.google.com [209.85.219.164]) by mx1.freebsd.org (Postfix) with ESMTP id E05258FC17 for ; Tue, 2 Jun 2009 08:52:20 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: by ewy8 with SMTP id 8so4996886ewy.43 for ; Tue, 02 Jun 2009 01:52:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:in-reply-to:x-mimeole:thread-index; bh=3LPzc3IKFcs2xj89xxpSR6d7vIvJz/u9bkJe5cP2bQY=; b=a3HzFf7LsjqGyIvqsJiyq0g10EljhZM7uvAu+9yXDRmssjvnq1LG0erLJFPIAUZgjF o4dKwXF/gbs6Ga3X/+fM4KV5RUVAFiEbNK5DidxrUAhkAxw8tCxCCFzIXRNGgmzSwlUS KCYu5e6E+5Qx6ZaCvPCh+/a1sx/b0ImdH1PIU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:in-reply-to :x-mimeole:thread-index; b=i0jPyq++VUBLfAaxRinCDM5UY0LvBt65tQvJ8d7ey8see6mHPEg2Frg+KC5D3WfQfK JmNeOkZT+nQ6fkMkR7KXOJxezFA74g5nGYNj0AMUE4g2zqwBfHyIJ+6UyBDAVGs0yDUi 3F5s3Kz+ED5RSIQmLAx/71VcgJkiaBgEGWGqQ= Received: by 10.211.196.13 with SMTP id y13mr7266869ebp.8.1243932739123; Tue, 02 Jun 2009 01:52:19 -0700 (PDT) Received: from LTPCSCOTT (e1-1.ns500-1.ts.milt.as9105.net [212.74.112.53]) by mx.google.com with ESMTPS id 4sm8531649ewy.80.2009.06.02.01.52.18 (version=SSLv3 cipher=RC4-MD5); Tue, 02 Jun 2009 01:52:18 -0700 (PDT) From: krad To: "'Wojciech Puchar'" , "'krad'" References: <20090530175239.GA25604@logik.internal.network><20090530144354.2255f722@bhuda.mired.org><20090530191840.GA68514@logik.internal.network><20090530162744.5d77e9d1@bhuda.mired.org><20090531201445.GA82420@logik.internal.network><0229B3BF1BE94C82AA11FD06CBE0BDEF@uk.tiscali.intl><20090531235943.GA77374@logik.internal.network><20090531201408.45dd4334@bhuda.mired.org> <442651299CA2445991E65F64AF9E65D7@uk.tiscali.intl> <3ED3189838484C8FBDECE5478A0DDFF4@uk.tiscali.intl> Date: Tue, 2 Jun 2009 09:52:17 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: Acni0KB3ofsuHXpSRz2D7D/ddsTadAAjfzGA X-Mailman-Approved-At: Tue, 02 Jun 2009 11:20:07 +0000 Cc: freebsd-hackers@freebsd.org, 'Mike Meyer' , xorquewasp@googlemail.com Subject: RE: Request for opinions - gvinum or ccd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2009 08:52:21 -0000 " You need to write a program that will just rewrite all files to make this." No you don't you just make sure you scrub the pools regularly once a week for instance. This way you will hopefully see small block error way before you have a full drive failure. At the end of the day if the data is super critical to you then you should follow best practices and build an array with sufficient amount of redundancy in for you needs. If you cant justify getting 4+ drives to build a raidz2 or raid 10 type scenario then the data on said array cant actually be worth much itself, therefore I might be annoying but in the whole scale of things not that costly if you loose it. If it were you would do thing properly in the first place -----Original Message----- From: Wojciech Puchar [mailto:wojtek@wojtek.tensor.gdynia.pl] Sent: 01 June 2009 16:50 To: krad Cc: 'Mike Meyer'; freebsd-hackers@freebsd.org; xorquewasp@googlemail.com Subject: RE: Request for opinions - gvinum or ccd? > Its all done on write, so if you update the file it will have multiple > copies again what is exactly what i said in the beginning.