From owner-freebsd-fs@FreeBSD.ORG Sat Jun 6 11:54:34 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 DDDC71065670 for ; Sat, 6 Jun 2009 11:54:34 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: from mail-fx0-f214.google.com (mail-fx0-f214.google.com [209.85.220.214]) by mx1.freebsd.org (Postfix) with ESMTP id 749078FC1A for ; Sat, 6 Jun 2009 11:54:34 +0000 (UTC) (envelope-from yan.batuto@gmail.com) Received: by fxm10 with SMTP id 10so74713fxm.43 for ; Sat, 06 Jun 2009 04:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type:content-transfer-encoding; bh=bwF9i5ptWDcH3dXc8NXudVel1N6k5o/wC3nK6TRtGD4=; b=utABS+KAP8dYvapYdS4ey5C4VloIhzniiQNSVGNHY3zbispf0+LWMJq7wXkODpLN/+ tup3N3YmxDfEt4mgb5xaLgxS+wMxqaTZUUMWOgmeXr2rvJvUhJRq05vKVpk4BL4k/bcf n1JIRUzgSAJOpeVejuBASHN9KkC1hU1rbIing= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=rT+lbZTwnlkxzWxSVcbiv5RMWrx1IE8tTBpSRFmEXQrylxWqCUQ9Z0R2DzjH4DMIKM vKHHMRKeyBtq9rKG0LU/gWnsa4bi87oUfPIuNcqsaI7XVrKHiwzmAksr7jA97Unj0Aom D+VOs+AzjRbflDmcrWYSzY67/DQhGXshic3wk= MIME-Version: 1.0 Received: by 10.239.180.146 with SMTP id i18mr340283hbg.142.1244287934068; Sat, 06 Jun 2009 04:32:14 -0700 (PDT) From: "Yan V. Batuto" Date: Sat, 6 Jun 2009 15:31:54 +0400 Message-ID: To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: 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: Sat, 06 Jun 2009 11:54:35 -0000 Hello! RAID-Z v6 works OK with 7.2-RELEASE, but it fails with recent 7.2-STABLE. -------------------------------------------------- # zpool status bigstore pool: bigstore state: ONLINE scrub: scrub completed with 0 errors on Fri Jun 5 22:28:19 2009 config: NAME STATE READ WRITE CKSUM bigstore ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 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 state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://www.sun.com/msg/ZFS-8000-5E scrub: none requested config: NAME STATE READ WRITE CKSUM bigstore UNAVAIL 0 0 0 insufficient replicas raidz1 UNAVAIL 0 0 0 insufficient replicas ad8 FAULTED 0 0 0 corrupted data ad10 FAULTED 0 0 0 corrupted data ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 0