[Bug 248907] zpool doesn't boot anymore on 12.1-STABLE after pool expansion

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248907

            Bug ID: 248907
           Summary: zpool doesn't boot anymore on 12.1-STABLE after pool
                    expansion
           Product: Base System
           Version: 12.1-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: halfling at halfling.com.br

Created attachment 217522
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=217522&action=edit
zpool doesnt boot

Hi there,

I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I added two
more disks to expand my pool. BTW I already did it many time with no issues.

I ran: 

# zpool status
  pool: zroot
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: none requested
config:

        NAME         STATE     READ WRITE CKSUM
        zroot        ONLINE       0     0     0
          gpt/disk0  ONLINE       0     0     0

errors: No known data errors

# zpool add -f zroot da1
# zpool add -f zroot da2
# zpool status
  pool: zroot
 state: ONLINE
  scan: none requested
config:

        NAME         STATE     READ WRITE CKSUM
        zroot        ONLINE       0     0     0
          gpt/disk0  ONLINE       0     0     0
          da1        ONLINE       0     0     0
          da2        ONLINE       0     0     0

errors: No known data errors
# reboot

Then my system doesn’t boot anymore, i got the following error:

See errors in my attachment

I can import my pool with no problems using the lived, but I could not fix it.

Seems a bug after 12.1-STABLE. Please, anyone can take a look ok that?

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.