freebsd stable - May 2017 - zpool imported twice with different names (was Re: Fwd: ZFS)

Nikos Vassiliadis <nvass at gmx.com> wrote:
> 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 at 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 at 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 at 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
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170516/d787fac8/attachment.sig>

On 05/16/2017 05:08 PM, Fabian Keil wrote:
> 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.
If you boot from another system, there is no other way to
import a pool than using "import -f". So, I guess it is
part of normal administrative tasks. You can read more here:
> http://docs.oracle.com/cd/E19253-01/819-5461/gazuf/index.html
This works and always have worked as documented.
Renaming a pool also works as documented, that is,
doing "zpool import oldnamepool newnamepool". Except
for this corner-case. IMHO this is a very serious bug.

Best,
Nikos