zpool imported twice with different names (was Re: Fwd: ZFS)
Eric A. Borisch
eborisch at gmail.com
Sat May 20 03:57:16 UTC 2017
On Thu, May 18, 2017 at 9:18 AM, Eric A. Borisch <eborisch at gmail.com> wrote:
> On Wed, May 17, 2017 at 9:38 PM, Eric A. Borisch <eborisch at gmail.com>
> wrote:
>
>> 4) zpool import -f alpha beta succeeds without any complaints.
>>
>> IV. Alpha no longer exists, Beta exists (with the same GUID as Alpha) AND
>> is active. This is an 'atomic' operation from user's point of view, and at
>> no point does zpool list show more than one pool
>>
>> 5) zpool list shows only beta; scrubs fine, life is good..
>>
>> V. Beta exists on disk and is active and healthy. Alpha is no more.
>> (Except as a ghost in a cache file)
>>
>
> A quick test revealed one other tidbit this morning; if I 'zpool export
> beta' at this point in the process (still in live CD OS), everything is OK
> on reboot into the installed OS.
>
> For whoever wants to investigate handling/hand-off between
> bootloader/kernel/fully booted, the problem appears when a:
>
> 1) root pool is renamed, but not 'zpool export'-ed after rename via an
> 'external' OS (live CD)
> ** and **
> 2) A stale zpool.cache file exists on the pool referring to the original
> name.
>
bug report created: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219411
More information about the freebsd-fs
mailing list