From owner-freebsd-fs@FreeBSD.ORG Fri Apr 5 11:14:40 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A628A866 for ; Fri, 5 Apr 2013 11:14:40 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.18.16]) by mx1.freebsd.org (Postfix) with ESMTP id 6C074F78 for ; Fri, 5 Apr 2013 11:14:40 +0000 (UTC) Received: from [87.79.197.81] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1UO4K0-0005X0-I8; Fri, 05 Apr 2013 12:56:40 +0200 Date: Fri, 5 Apr 2013 12:56:40 +0200 From: Fabian Keil To: freebsd-fs@freebsd.org Subject: Re: Error ZFS-8000-8A on 9.1 under VMware Message-ID: <20130405125635.41478c64@fabiankeil.de> In-Reply-To: <20130405131954.60183@relay.ibs.dn.ua> References: <20130405131954.60183@relay.ibs.dn.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/n3vvZPfS.kyonTgUyN.Rc1X"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2013 11:14:40 -0000 --Sig_/n3vvZPfS.kyonTgUyN.Rc1X Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Zeus Panchenko wrote: > I face weird situation ... may somebody advice, please? >=20 > Under VMware ESX 4.1.2 two FreeBSD-9.1-amd64-on-ZFS boxes were set. > on both of them open-vm-tools are installed >=20 > after some time of correct functionality, I'm getting error ZFS-8000-8A > on both of the boxes ... >=20 > after corrupted files removal and `zpool clean' no errors reported by > `zpool scrub' Are you sure the "Permanent errors" are (or were) actually permanent? If they are, you should get an error message when cat'ing the supposedly affected files to /dev/null and the files should show up again when scrubbing the pool without deleting any files first. Depending on the error, reading the files again can also trigger kernel messages that could be useful to analyse the problem. I'm not using VMware, but in my experience ZFS treats some temporary errors in non-redundant configurations as permanent until the pool is scrubbed. It happens rarely, so I haven't properly looked into this yet. Fabian --Sig_/n3vvZPfS.kyonTgUyN.Rc1X Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFeregACgkQBYqIVf93VJ3IRACgji6sjP+71hkOXTdzBMZveuNo X/AAoLiMGNdRDOcdecJ0b41jopZlX4kf =hdi+ -----END PGP SIGNATURE----- --Sig_/n3vvZPfS.kyonTgUyN.Rc1X--