From owner-freebsd-fs@FreeBSD.ORG Fri Nov 9 15:40:01 2012 Return-Path: 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 E5F0C6DA for ; Fri, 9 Nov 2012 15:40: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 B348A8FC0C for ; Fri, 9 Nov 2012 15:40: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 qA9Fe1QC063614 for ; Fri, 9 Nov 2012 15:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qA9Fe1Dc063613; Fri, 9 Nov 2012 15:40:01 GMT (envelope-from gnats) Date: Fri, 9 Nov 2012 15:40:01 GMT Message-Id: <201211091540.qA9Fe1Dc063613@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org Cc: From: Guido Falsi 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: Guido Falsi List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2012 15:40:02 -0000 The following reply was made to PR kern/150503; it has been noted by GNATS. From: Guido Falsi To: Andriy Gapon Cc: bug-followup@FreeBSD.org, william.franck@oceasys.net, Martin Matuska Subject: Re: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot Date: Fri, 09 Nov 2012 16:34:54 +0100 On 11/09/12 16:14, Andriy Gapon wrote: >> 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. > I also tried making make installkernel ; make installworld ; reboot, but had the same symptoms. luckily I was also able to rollback to a previous zfs snapshot from the USB key after the export/import trick. >> 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... > Uhm I don't know how to generate a new zpool.cache from a newly update system, since I can't export/import the root and don't have a newer system on a USB key. I'll have to produce one perhaps. -- Guido Falsi