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

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

On Wed, May 17, 2017 at 2:04 PM, Nikos Vassiliadis <nvass at gmx.com>
wrote:
> 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.
>
Sorry, no, that's not a bug. The bug is that, if importing on another
system is a common administrative operation, it should not require you to
disable *all* checking. I'd rather prefer specific support for that, e.g.
"import -F expectedhostname" to import a zpool on a different host
from
expectedhostname --- now you have sanity checking for a potentially
dangerous operation as well as not turning off *all* error/sanity checking.

Sadly, this seems to not have occurred to either Sun or Oracle, despite
having documented it.

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at
sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net