zpool imported twice with different names (was Re: Fwd: ZFS)

[Paul Kraus]

> On May 17, 2017, at 2:13 PM, Brandon Allbery <allbery.b at gmail.com> wrote:
> 
> 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.

The assumption at work here is that you have exported the zpool from the system that was using it. At that point, zpool import <poolname> with no -f will work fine. It is only the special case of a zpool that was NOT exported that requires the use of the -f option.

I don’t see this as an unreasonable expectation. You unmount non-ZFS (and under the covers ZFS) filesystems before moving them to other systems. Why should we not be expected to export a zpool before moving it ?

Note that in the case of a crashed or failed or otherwise _unexpected_ move of a zpool from one system to another you still need to force the import. Just as you are forced to either fsck or replay journals on non-ZFS filesystems before you can mount them.