10.0-BETA4 (upgraded from 9.2-RELEASE) zpool upgrade -> boot failure

[Artem Belevich]

On Thu, Dec 12, 2013 at 3:16 PM, Florent Peterschmitt
<florent at peterschmitt.fr> wrote:
> Le 12/12/2013 22:04, Artem Belevich a écrit :
>> On Thu, Dec 12, 2013 at 1:12 PM, Florent Peterschmitt
>> <florent at peterschmitt.fr> wrote:
>>>> do  "zdb -l /dev/ada0" (and all other slices on ada0) and check
>>>> whether it reports anything unexpected.
>>>>
>>>> --Artem
>>>
>>> rescue-bsd# zdb -l /dev/ada0
>>> --------------------------------------------
>>> LABEL 0
>>> --------------------------------------------
>>> failed to unpack label 0
>>> --------------------------------------------
>>> LABEL 1
>>> --------------------------------------------
>>> failed to unpack label 1
>>> --------------------------------------------
>>> LABEL 2
>>> --------------------------------------------
>>> failed to unpack label 2
>>> --------------------------------------------
>>> LABEL 3
>>> --------------------------------------------
>>> failed to unpack label 3
>>>
>>>
>>> Well… this sounds bad, right?
>>
>> This looks the way it's supposed to -- no unwanted ZFS pool info is found.
>>
>> Now repeat that for all ada0p? and make sure only the slice that's
>> part of your pool shows ZFS labels and only for one pool.
>>
>> Think a bit about how bootloader figures out how your pool is built.
>> All it has access to is a raw disk and partition table. So in order to
>> find the pool it probes raw disk and all partitions trying to find ZFS
>> labels and then uses info in those labels to figure out pool
>> configuration. If bootloader finds stale ZFS labels left from a
>> previous use of the disk in some other pool, it would potentially mess
>> up detection of your real boot pool.
>>
>> --Artem
>>
>
> rescue-bsd# zdb -l /dev/ada0p1

...[snip]...

> --------------------------------------------
> LABEL 3
> --------------------------------------------
>     version: 5000
>     name: 'tank'
>     state: 0
>     txg: 1248416
>     pool_guid: 14109252772653171024
>     hostid: 1349238423
>     hostname: 'rescue-bsd.ovh.net'
>     top_guid: 8826573031965252809
>     guid: 8826573031965252809
>     vdev_children: 1
>     vdev_tree:
>         type: 'disk'
>         id: 0
>         guid: 8826573031965252809
>         path: '/dev/gpt/zfs-root'
>         phys_path: '/dev/gpt/zfs-root'
>         whole_disk: 1
>         metaslab_array: 30
>         metaslab_shift: 32
>         ashift: 9
>         asize: 493660405760
>         is_log: 0
>         create_txg: 4
>     features_for_read:
>
>
> Since freebsd-zfs is installed on ada0p3, it's normal to get that. Then,
> what can you say about that?

Well, you've eliminated the possibility that there may be orphaned ZFS
labels messing up with the boot.

--Artem