From owner-freebsd-stable@FreeBSD.ORG Thu Dec 12 11:07:47 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3DE4AF46 for ; Thu, 12 Dec 2013 11:07:47 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8AA98147E for ; Thu, 12 Dec 2013 11:07:46 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA02914; Thu, 12 Dec 2013 13:07:17 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Vr46v-000KUs-C3; Thu, 12 Dec 2013 13:07:17 +0200 Message-ID: <52A99894.4080704@FreeBSD.org> Date: Thu, 12 Dec 2013 13:05:56 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "Eugene M. Zheganin" Subject: Re: zfs i/o error - all block copies unavailable References: <52A8C5AF.1000800@norma.perm.ru> In-Reply-To: <52A8C5AF.1000800@norma.perm.ru> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org Stable" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 11:07:47 -0000 on 11/12/2013 22:06 Eugene M. Zheganin said the following: > Hi. > > I have a server, it was running 8.2-STABLE/i386 with zfs v28. All of a sudden, > on last reboot I got a big bunch of "zfs i/o error - all block copies > unavailable" messages and server was unable to boot. I decided that one disk is > dying, detached it, and booted successfully. On a next boot I got this again. I > booted from CD, replaced a zpool.cache, and booted successfully once again. On > next reboot I got it again, and was unable to fix it. However (as you may > already know) disks were fine, and all the data wasn't corrupted. Iread a couple > of mailing list posts about this mentioning that this could be an i386 issue, > and decided to deal with in a radical way: I've installed 10.0-BETA1/amd64 > (booted from a LiveCD, mounted an NFS share with /usr/src and obj, and did the > upgrade). Now everything is almost fine, except that I still get this message, > but only once and it seems to be harmless, as the server can still be booted (I > experimented and tried this like a dozen times). > > So, questions: > > - is it really harmless ? > - can I run with this ? > - is there any way to get rid of it ? (probably, without recreating a pool, > because it holds several TBytes of user data) > - and, finally - what does it mean ? A few words about your pool configuration and the disks that it is comprised of... -- Andriy Gapon