From owner-freebsd-fs@freebsd.org Mon May 15 18:11:41 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A77FD6E25A; Mon, 15 May 2017 18:11:41 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B0AF1580; Mon, 15 May 2017 18:11:40 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from iris.berlin.strato.de ([192.166.200.216]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0MdK8t-1dS8AT3Ebj-00IV1p; Mon, 15 May 2017 20:11:38 +0200 Subject: zpool imported twice with different names (was Re: Fwd: ZFS) From: Nikos Vassiliadis To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org References: <7c059678-4af4-f0c9-ff3b-c6266e02fb7a@gmx.com> Message-ID: Date: Mon, 15 May 2017 20:11:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:uLu4BIUWtdJ0ahoKpW3EEJSRvJQccXKvHLT3RdCAMbuDayOh7uf iralYDcwSiyjy7/zpuydwSKHO4cQdC99VxY+hY8dRV8lMAF57REOfnwQMfRrkJe5WWfEl7h QFJCv+eDEKe2pgyNKnkCt2aaqjjz0fEAauQtfi4RP1Yt52h1i4ZdQM8H3Kq2zgr8c+hfsOq fmsfiptoRVHA9RXrkKQQg== X-UI-Out-Filterresults: notjunk:1;V01:K0:8KRWvFFTzcE=:S0+rVJV1sfmAzdUvB6I2Ai p5MpV+or3wVdGdW7EjTO+5ieijzyHwpUhcfYKJRHrmRS3G4z43YyMKLsCIQYF7ha1eJbbjBkm 1M5x5qJXFlWSbeYYzchWJmERTVtMHTpnAxA+HJ/8TluXKVSuEb9ltjloK5iuBoadjICxJs+vT LGNRFBoAt3taga6Y7SZDCE7WIaxTwd04MKWJsPpCzNd4sazjZXkCA3u7U4fpdWhuSGR5ZqByd S2obvxs0gEiK5AbGxHMlKi8mO4P+wYkt4yDl5rChQO1WZaOPA1n8bUHhobmKacyHbyk0i52y/ wZ6rT785eY4y9et6LlktXXZKAVkDfMQgHh9gc4EEyaR6aShyVbWfzm6KftURKRkcOrLaxNEd1 dmQiFG1WMtxCbmrQwlK2rDyXBqsWbK/NmWaqLPcL4b8rHOw2ZmDpOORx8QH90BXEXy3eiykgP pdIRwhdkoIhQIFQFg7Q0b8HWbamWHkIYY0AVhvsehLHzGcvpjcIsPWOz6rAaB877lVpCVCp5S S2iKubvvzMd4x9+eorEOnLkuOKZTCm04bnjCTk83ouf6RNu2H0xUBhcfTc1kramSjkx+2GSzs sexiN7aJ1HGkkGIMjBY1WNSTTeQTPyFYUDqII0tiZDj7WkHEw8PKCq5ZHFG6hObdPkzgC3Kd4 fG8DC+iQ2NPhwm8u+E5zpH+6Tqzf0cQ4H5Y+UFDeT4AmsIZ+cHhg6+oaarTU/f5MERLjd1fTW OBeIVplx9A9RIsJofOGhq7xDWIbRgnXLDjL/ftX2g+6o9N6zFMr3ZIFd5ROV2tIE5IhqFmcFx ZO664zc X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2017 18:11:41 -0000 Fix the e-mail subject On 05/15/2017 08:09 PM, Nikos Vassiliadis wrote: > Hi everybody, > > While trying to rename a zpool from zroot to vega, > I ended up in this strange situation: > nik@vega:~ % zfs list -t all > NAME USED AVAIL REFER MOUNTPOINT > vega 1.83G 34.7G 96K /zroot > vega/ROOT 1.24G 34.7G 96K none > vega/ROOT/default 1.24G 34.7G 1.24G / > vega/tmp 120K 34.7G 120K /tmp > vega/usr 608M 34.7G 96K /usr > vega/usr/home 136K 34.7G 136K /usr/home > vega/usr/ports 96K 34.7G 96K /usr/ports > vega/usr/src 607M 34.7G 607M /usr/src > vega/var 720K 34.7G 96K /var > vega/var/audit 96K 34.7G 96K /var/audit > vega/var/crash 96K 34.7G 96K /var/crash > vega/var/log 236K 34.7G 236K /var/log > vega/var/mail 100K 34.7G 100K /var/mail > vega/var/tmp 96K 34.7G 96K /var/tmp > zroot 1.83G 34.7G 96K /zroot > zroot/ROOT 1.24G 34.7G 96K none > zroot/ROOT/default 1.24G 34.7G 1.24G / > zroot/tmp 120K 34.7G 120K /tmp > zroot/usr 608M 34.7G 96K /usr > zroot/usr/home 136K 34.7G 136K /usr/home > zroot/usr/ports 96K 34.7G 96K /usr/ports > zroot/usr/src 607M 34.7G 607M /usr/src > zroot/var 724K 34.7G 96K /var > zroot/var/audit 96K 34.7G 96K /var/audit > zroot/var/crash 96K 34.7G 96K /var/crash > zroot/var/log 240K 34.7G 240K /var/log > zroot/var/mail 100K 34.7G 100K /var/mail > zroot/var/tmp 96K 34.7G 96K /var/tmp > nik@vega:~ % zpool status > pool: vega > state: ONLINE > scan: scrub repaired 0 in 0h0m with 0 errors on Mon May 15 01:28:48 2017 > config: > > NAME STATE READ WRITE CKSUM > vega ONLINE 0 0 0 > vtbd0p3 ONLINE 0 0 0 > > errors: No known data errors > > pool: zroot > state: ONLINE > scan: scrub repaired 0 in 0h0m with 0 errors on Mon May 15 01:28:48 2017 > config: > > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > vtbd0p3 ONLINE 0 0 0 > > errors: No known data errors > nik@vega:~ % > ------------------------------------------- > > It seems like there are two pools, sharing the same vdev... > > After running a few commands in this state, like doing a scrub, > the pool was (most probably) destroyed. It couldn't boot anymore > and I didn't research further. Is this a known bug? > > Steps to reproduce: > install FreeBSD-11.0 in a pool named zroot > reboot into a live-CD > zpool import -f zroot vega > reboot again > > Thanks, > Nikos > > PS: > Sorry for the cross-posting, I am doing this to share to more people > because it is a rather easy way to destroy a ZFS pool. >