From owner-freebsd-fs@FreeBSD.ORG Sun May 6 16:10:38 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0142B106566C for ; Sun, 6 May 2012 16:10:38 +0000 (UTC) (envelope-from hackish@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B9AE88FC08 for ; Sun, 6 May 2012 16:10:37 +0000 (UTC) Received: by obcni5 with SMTP id ni5so9323252obc.13 for ; Sun, 06 May 2012 09:10:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8y9KXQV4GF7qHdAM7JvLjffQyrDkEru4ESwm53v57tM=; b=Bq3tnaqrOytkqU2Ro7yquYVddufuVVDLVd+E1GEEV3+TF5N94HFk6/fL0juFHXFVEc isprUDv7o8XTpe8qzd8X+fCmft1iMGvisg7weLnVLXSkEkTxT9R/FOAapTdjWnnMr+ZS 8bxKRobiw42GCm2zouYJvyxX/G2/kwS8c8idTdcaXqWrRzII94Vzshnj4IOiyehX3Etx A/cLV5BeVkp740bEL1FmcUiQ0c5czUPLR7JxMAniy8CyhIrpgRDMwbZGbAEKhII9kFIT 21szhAX+ZxXjVjJszLo1zx9cOCr8Lg3x6eNfkuRKkkQJPMgAd6Ox5EWMAti2WkMKw/sK Vp1w== MIME-Version: 1.0 Received: by 10.182.167.101 with SMTP id zn5mr6197992obb.13.1336320637350; Sun, 06 May 2012 09:10:37 -0700 (PDT) Received: by 10.182.27.130 with HTTP; Sun, 6 May 2012 09:10:37 -0700 (PDT) In-Reply-To: References: <20120506123826.412881065672@hub.freebsd.org> Date: Sun, 6 May 2012 12:10:37 -0400 Message-ID: From: Michael Richards To: Bob Friesenhahn Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" Subject: Re: ZFS Kernel Panics with 32 and 64 bit versions of 8.3 and 9.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 May 2012 16:10:38 -0000 On Sun, May 6, 2012 at 10:59 AM, Bob Friesenhahn wrote: > On Sun, 6 May 2012, Simon wrote: > >> >> Are you suggesting that if a disk sector goes bad or memory corrupts few >> blocks >> of data, the entire zpool is gonna go bust? can the same occur with a >> ZRAID? >> I thought the ZFS was designed to overcome all these issues to begin with. >> Is >> this not the case? > > > ZFS is designed to work with failing disks, but not failing memory. It is > recommended to use only systems with ECC memory. > > The OS itself (any OS!) is succeptible to crash/corruption due to failing > memory but without zfs's checksums, you might not be aware of such > corruptions or the crash might be more delayed. I can accept the fact that some filesystem corruption may have happened from the bad RAM. The issue now is recovering it. All the hardware has been replaced but I cannot import the ZFS pool without causing a kernel panic and that is the the problem here. To me it matters not if the corruption occurred from RAM or the hard disk - I don't think it's a good idea to blindly trust any filesystem data. At minimum fail to import the pool but don't bring the entire system to a halt. This isn't even a system drive - it's purely data.