From owner-freebsd-fs@FreeBSD.ORG  Fri Nov  9 15:20:01 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id A4E6D244
 for <freebsd-fs@hub.freebsd.org>; Fri,  9 Nov 2012 15:20:01 +0000 (UTC)
 (envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 by mx1.freebsd.org (Postfix) with ESMTP id 7177C8FC14
 for <freebsd-fs@hub.freebsd.org>; Fri,  9 Nov 2012 15:20:01 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qA9FK1Pn063066
 for <freebsd-fs@freefall.freebsd.org>; Fri, 9 Nov 2012 15:20:01 GMT
 (envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
 by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA9FK1qZ063065;
 Fri, 9 Nov 2012 15:20:01 GMT (envelope-from gnats)
Date: Fri, 9 Nov 2012 15:20:01 GMT
Message-Id: <201211091520.qA9FK1qZ063065@freefall.freebsd.org>
To: freebsd-fs@FreeBSD.org
Cc: 
From: Andriy Gapon <avg@FreeBSD.org>
Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after
 reboot
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Andriy Gapon <avg@FreeBSD.org>
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 15:20:01 -0000

The following reply was made to PR kern/150503; it has been noted by GNATS.

From: Andriy Gapon <avg@FreeBSD.org>
To: bug-followup@FreeBSD.org, Guido Falsi <mad@madpilot.net>
Cc: william.franck@oceasys.net, Martin Matuska <mm@FreeBSD.org>
Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after
 reboot
Date: Fri, 09 Nov 2012 17:14:52 +0200

 >    pool: tank
 >    state: UNAVAIL
 >  status: One or more devices could not be opened.  There are insufficient
 >           replicas for the pool to continue functioning.
 >  action: Attach the missing device and online it using 'zpool online'.
 >      see: http://illumos.org/msg/ZFS-8000-3C
 >     scan: none requested
 >  config:
 >  
 >           NAME                      STATE     READ WRITE CKSUM
 >           tank                      UNAVAIL      0     0     0
 >             mirror-0                UNAVAIL      0     0     0
 >               13149740312808713750  UNAVAIL      0     0     0  was 
 >  /dev/gpt/disk0
 >               6984386892400701167   UNAVAIL      0     0     0  was 
 >  /dev/gpt/disk1
 >             mirror-1                UNAVAIL      0     0     0
 >               10066834453677312324  UNAVAIL      0     0     0  was 
 >  /dev/gpt/disk2
 >               571766486195567663    UNAVAIL      0     0     0  was 
 >  /dev/gpt/disk3
 
 
 Commenting only on this piece.  After some ZFS changes from about a month ago you
 can get this kind of output if your ZFS userland is older than your kernel ZFS.
 If this is the case, the then above message is just symptom of that discrepancy.
 
 > Trying to mount root from zfs:tank []...
 >  Mounting from zfs:tank failed with error 22
 
 22 is EINVAL, not sure how to interpret this failure.
 Could be a result of zpool.cache being produced by the older code, but not sure...
 
 -- 
 Andriy Gapon