Comment 4 for bug 1881810

Revision history for this message
Andreas Mattisson (andreasmatt) wrote :

Thanks for you fast reply.

This is the same behaviour from bug: 1880580, that I wrote.
I have updated and can only continue verify on the latest 20.04, not 18.04 anymore.
This is what I have done so far now.

I tried you suggested solution. I first had to remove /etc/zfs/zpool.cache in order to be able to do this.

Then I tried your solution 2 times, once with no flags, and then with -f flag.
The panic still occurs when doing this.

Should I try zdb again?
Any other suggestions ?

# cat /sys/module/zfs/parameters/spa_load_verify_metadata
1
# echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_metadata
0
# echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_data
0
# zpool import
   pool: datastore
     id: 3190464655986727485
  state: ONLINE
 status: Some supported features are not enabled on the pool.
 action: The pool can be imported using its name or numeric identifier, though
        some features will not be available without an explicit 'zpool upgrade'.
 config:

        datastore ONLINE
          raidz2-0 ONLINE
            sdb ONLINE
            sdc ONLINE
            sdd ONLINE
            sde ONLINE
            sdf ONLINE
            sdg ONLINE
# zpool import datastore
or
# zpool import -f datastore

Cause this output:
VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (...)
PANIC at zio.c:293:zio_buf_alloc()