Date: Tue, 16 May 2017 17:08:02 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zpool imported twice with different names (was Re: Fwd: ZFS) Message-ID: <20170516170802.71c2a470@fabiankeil.de> In-Reply-To: <ca7b47a7-7512-3cbb-d47b-6ef546dffd74@gmx.com> References: <7c059678-4af4-f0c9-ff3b-c6266e02fb7a@gmx.com> <adf4ab9f-72f1-ed0f-fee2-82caba3af4a4@gmx.com> <ca7b47a7-7512-3cbb-d47b-6ef546dffd74@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Ux+_Pdaq.tM_nalOv235In9 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Nikos Vassiliadis <nvass@gmx.com> wrote: > On 05/15/2017 08:09 PM, Nikos Vassiliadis wrote: > > Hi everybody, > >=20 > > 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: > >=20 > > NAME STATE READ WRITE CKSUM > > vega ONLINE 0 0 0 > > vtbd0p3 ONLINE 0 0 0 > >=20 > > errors: No known data errors > >=20 > > pool: zroot > > state: ONLINE > > scan: scrub repaired 0 in 0h0m with 0 errors on Mon May 15 01:28:48 > > 2017 config: > >=20 > > NAME STATE READ WRITE CKSUM > > zroot ONLINE 0 0 0 > > vtbd0p3 ONLINE 0 0 0 > >=20 > > errors: No known data errors > > nik@vega:~ % > > ------------------------------------------- > >=20 > > It seems like there are two pools, sharing the same vdev... > >=20 > > 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? > >=20 > > Steps to reproduce: > > install FreeBSD-11.0 in a pool named zroot > > reboot into a live-CD > > zpool import -f zroot vega Why did you use the -f flag? Unless you can reproduce the problem without it, it's not obvious to me that this is a bug. Fabian --Sig_/Ux+_Pdaq.tM_nalOv235In9 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCWRsV0wAKCRAFiohV/3dU nU8JAKC5MOZFsHNKd0Ry4lkGNtpmLqimEwCgu28OsdQ1UNF+ft4TJZFd0VFneLc= =Qj7V -----END PGP SIGNATURE----- --Sig_/Ux+_Pdaq.tM_nalOv235In9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170516170802.71c2a470>