From owner-freebsd-fs@FreeBSD.ORG Sun Jun 7 12:55:44 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C20851065672 for ; Sun, 7 Jun 2009 12:55:44 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by mx1.freebsd.org (Postfix) with ESMTP id 41FC18FC1D for ; Sun, 7 Jun 2009 12:55:43 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: by fxm11 with SMTP id 11so201137fxm.43 for ; Sun, 07 Jun 2009 05:55:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=oe1hpDlw0GPoZmh9Q3iKMtUOq904yM0EiRkDMuKro3E=; b=psfAgPmVoLoMeCWglS6tbvtPLiQg7Er1kmAFtCToVYQt7kG+aftRApZ71zV7w1wpH2 ftOv2fD2/++8GPdtzO6kzjQltKKztlxxGJGHNO2rYvgVIepKAzTFvqVn1jAE+W/HOxIz g1ns41hhI4w6zKSgykF7zHNLCLvNUo0KrtfNU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=LIQ5xsa0Jj0apIfmbapxbJ3BGGoOHsqp0IsOsTloPUGkorr7UTmGnBB7S9RRqewdkF yoWV0+Y9GbasfNCE5uYVs1dq2MCnej6FVMUNkoJdlR0x5cwJ0QtMaC5scSpPT3x9SpA4 nUB7KqNSvwwpSMiLqkyDqelEcoizJx5ZE+jx8= MIME-Version: 1.0 Received: by 10.239.179.19 with SMTP id b19mr400480hbg.2.1244379343066; Sun, 07 Jun 2009 05:55:43 -0700 (PDT) In-Reply-To: <4A2A7DE4.1080008@egr.msu.edu> References: <4A2A7DE4.1080008@egr.msu.edu> From: "Yan V. Batuto" Date: Sun, 7 Jun 2009 16:55:23 +0400 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Strange ZFS pool failure after updating kernel v6->v13 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, 07 Jun 2009 12:55:45 -0000 2009/6/6 Adam McDougall : > Yan V. Batuto wrote: >> >> Hello! >> >> RAID-Z v6 works OK with 7.2-RELEASE, but it fails with recent 7.2-STABLE= . >> -------------------------------------------------- >> # zpool status bigstore >> =A0pool: bigstore >> =A0state: ONLINE >> =A0scrub: scrub completed with 0 errors on Fri Jun =A05 22:28:19 2009 >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM >> =A0 =A0 =A0 =A0bigstore =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 >> =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 = 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad4 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad6 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad8 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> >> errors: No known data errors >> -------------------------------------------------- >> After cvsup to 7-STABLE, usual procedure of rebuilding kernel and >> world, and reboot pool is failed. >> It's quite strange that now pool consists of ad8, ad10, and again ad8, >> ad10 drives instead of ad4, ad6, ad8, ad10. >> >> I removed additional disk controller few weeks ago, so raid-z >> originally was created as ad8+ad10+ad12+ad14, and then >> it appeared to be ad4+ad6+ad8+ad10. It was not a trouble for zfs v6, >> but, probably, something is wrong here in zfs v13. >> -------------------------------------------------- >> # zpool status bigstore >> pool: bigstore >> =A0state: UNAVAIL >> status: One or more devices could not be used because the label is missi= ng >> =A0 =A0 =A0 =A0or invalid. =A0There are insufficient replicas for the po= ol to >> continue >> =A0 =A0 =A0 =A0functioning. >> action: Destroy and re-create the pool from a backup source. >> =A0 see: http://www.sun.com/msg/ZFS-8000-5E >> =A0scrub: none requested >> config: >> >> =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM >> =A0 =A0 =A0 =A0bigstore =A0 =A0UNAVAIL =A0 =A0 =A00 =A0 =A0 0 =A0 =A0 0 = =A0insufficient replicas >> =A0 =A0 =A0 =A0 =A0raidz1 =A0 =A0UNAVAIL =A0 =A0 =A00 =A0 =A0 0 =A0 =A0 = 0 =A0insufficient replicas >> =A0 =A0 =A0 =A0 =A0 =A0ad8 =A0 =A0 FAULTED =A0 =A0 =A00 =A0 =A0 0 =A0 = =A0 0 =A0corrupted data >> =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0FAULTED =A0 =A0 =A00 =A0 =A0 0 =A0 = =A0 0 =A0corrupted data >> =A0 =A0 =A0 =A0 =A0 =A0ad8 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> =A0 =A0 =A0 =A0 =A0 =A0ad10 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 >> > > Please try: > zpool export bigstore > zpool import bigstore > > This should make it find the right hard drives if they are present, > otherwise should give a more informative error. > Thank you! I exported pool on 7.2-release, then upgraded to 7.2-stable and imported the pool back. All works OK.