From owner-freebsd-current@FreeBSD.ORG Tue Aug 28 18:03:43 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69B2B16A46C for ; Tue, 28 Aug 2007 18:03:43 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 0956613C4D3 for ; Tue, 28 Aug 2007 18:03:42 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 17C4045E94; Tue, 28 Aug 2007 20:03:42 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id ACAB545683; Tue, 28 Aug 2007 20:03:34 +0200 (CEST) Date: Tue, 28 Aug 2007 20:02:28 +0200 From: Pawel Jakub Dawidek To: Bakul Shah Message-ID: <20070828180228.GD39562@garage.freebsd.pl> References: <20070828165331.GA39562@garage.freebsd.pl> <20070828170242.1559F5B30@mail.bitblocks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uxuisgdDHaNETlh8" Content-Disposition: inline In-Reply-To: <20070828170242.1559F5B30@mail.bitblocks.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: current@FreeBSD.org, Pascal Hofstee Subject: Re: ZFS kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2007 18:03:43 -0000 --uxuisgdDHaNETlh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 28, 2007 at 10:02:42AM -0700, Bakul Shah wrote: > > When you don't use redundant configuration (no mirror, no raidz, no > > copies>1) then ZFS is going to panic on a write failure. It looks like > > ZFS found a bad block on your disk. >=20 > Does SUN really say this about ZFS? Is this acceptable in a > production environment? What if one of your mirrored disk > fails and in the "degraded" environment (before you have had > a chance to replace the bad disk) ZFS discovers that a write > fails? Why can't it find an alternative block to write to? There were many complains on zfs-discuss@, you may want to look into archive. The short version is that many users doesn't like that, and it should change in the future - because of COW model it should be quite easy to just mark block as bad and take next one, but it's not currently implemented. It's much less of a problem when one uses redundancy. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --uxuisgdDHaNETlh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG1GM0ForvXbEpPzQRArAmAKCxNQTAPw5zym9a0TmqJpp3ucombACfSJA4 9nv40SueyQal5WcwMKfWubw= =5NnR -----END PGP SIGNATURE----- --uxuisgdDHaNETlh8--