From owner-freebsd-questions@FreeBSD.ORG Fri Jun 27 22:33:57 2014 Return-Path: Delivered-To: freebsd-questions@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 32AF2C53 for ; Fri, 27 Jun 2014 22:33:57 +0000 (UTC) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0727424A3 for ; Fri, 27 Jun 2014 22:33:57 +0000 (UTC) Received: by mail-pa0-f53.google.com with SMTP id ey11so5193739pad.40 for ; Fri, 27 Jun 2014 15:33:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GsGEzULfF91vAk+P+V8x/jGmErRTWHC2tXK1KsC3qhI=; b=Xg8Fuocww1+g6wijkch3ksGxDyqt687MAacqsLFFDk5XG4Uk4qDazADayKnF/+nFWx cgc0v7yVxneZ+OgEuPROrOwNRaYWRTxda8c9GR2gCqYbt88z2lcEfeuRk+LjBk6x6ZWN RxernAaLRaGoLkhquMuzTSNVhqb+kr8terUUNctzTcSiLW8aubYBLamiczYYzNHSiYPw pokIjDWBKQQ08iSdHtEaMcYQiOdN5sKPe6bF87xuo0Avfg2DdBuuk+a8UTRzc1IJ1Qg1 HsiMLiqjL+iq+PDAc42eHmx2O6Jf4PgFOurfv6lQ3g62W3ivsFSVh/eAbITiJiu+RhX3 UaQA== MIME-Version: 1.0 X-Received: by 10.68.194.229 with SMTP id hz5mr33618793pbc.91.1403908435780; Fri, 27 Jun 2014 15:33:55 -0700 (PDT) Received: by 10.70.92.130 with HTTP; Fri, 27 Jun 2014 15:33:55 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Jun 2014 18:33:55 -0400 Message-ID: Subject: Re: FreeBSD 9.2-p9/FreeBSD 9.3-PRERELEASE zpool import/export problem From: FF To: =?UTF-8?Q?Trond_Endrest=C3=B8l?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2014 22:33:57 -0000 Thank you so much for a technical answer! I looked at the 9.3-RELEASE notes for any new features in ZFS and didn't see any listed, so I had assumed no new ones were implemented. I'm curious why creating a zpool under releng-9.2 didn't solve the problem after the fact? I even ran a complete drive wipe (dd if=3D/dev/zero of=3D/dev/{ada0-ada44} bs=3D16m) and the problem persisted. Thanks! On Fri, Jun 27, 2014 at 2:08 AM, Trond Endrest=C3=B8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Thu, 26 Jun 2014 21:28-0400, FF wrote: > > > So I'm having a weird problem that just came up when I went from > > freebsd-updated binaries to svn'ing the releng and/or stable source > trees. > > > > When I compile and build a kernel (only), I can create a zpool > > > > something like: > > > > zpool create tank ada1 > > > > I can use it, list it, create files on it, etc. > > > > I can zpool export it. > > > > It will still show as online an importable. > > > > But when I try to reimport it (no reboot or anything): > > > > root@1:/root # zpool create -f storage2 ada40 > > root@1:/root # df -kh > > Filesystem Size Used Avail Capacity Mounted on > > /dev/ada45s1a 7.9G 6.3G 990M 87% / > > devfs 1.0k 1.0k 0B 100% /dev > > storage2 913G 31k 913G 0% /storage2 > > root@1:/root # zpool export storage2 > > root@1:/root # zpool import > > pool: storage2 > > id: 10010508457819787577 > > state: ONLINE > > action: The pool can be imported using its name or numeric identifier. > > config: > > > > storage2 ONLINE > > ada40 ONLINE > > > > > > root@1:/root # zpool import storage2 > > cannot import 'storage2': pool is formatted using a newer ZFS version > > > > This happens repeatably whether its multi drive or single drive. > > > > root@1:/root # zfs upgrade > > This system is currently running ZFS filesystem version 5. > > > > All filesystems are formatted with the current version. > > > > > > root@1:/root # ls -al /sbin/z* > > -r-xr-xr-x 1 root wheel 96968 Feb 12 2013 /sbin/zfs > > -r-xr-xr-x 1 root wheel 92472 Feb 12 2013 /sbin/zpool > > root@1:/root # md5 /sbin/zfs > > MD5 (/sbin/zfs) =3D 76ddf1a93f9a045466ead1ef465859d0 > > root@1:/root # md5 /sbin/zpool > > MD5 (/sbin/zpool) =3D 29ec8f28ad5c6023ece4bb4eccb49f1e > > > > There's obviously no data on the system, so reformatting it with > > 9.2-RELEASE should fix it, but I'm trying to run a custom kernel and I'= m > > trying to figure out what I've screwed up along the way. Also, zpool > import > > -f does not solve it, same error. > > > > Any suggestions/advice on where this may have gone sideways? > > It's likely that your zpool created by stable/9 has enabled (and > activated some of) the following features: > > feature@multi_vdev_crash_dump > feature@spacemap_histogram > feature@enabled_txg > feature@hole_birth > feature@extensible_dataset > feature@bookmarks > feature@filesystem_limits > > They are unsupported by releng/9.2. Sadly, once a feature has been > enabled there's no going back. > > Either continue using stable/9, or when creating a zpool you intend > to use on older ZFS systems, try to avoid enabling any features > during pool creation, i.e. zpool create -d ... Afterwards you may > enable the features you know is supported across the board. > > Maybe someone else knows a better way. > > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=C3=B8l, | Trond Endrest=C3=B8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=C3=B8vik Technical College, Norway, = | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ --=20 FF