Solved [Solved] zpool import - Assertion failed

Pernat1y

Pernat1y

Hello.

I have no luck importing zfs pool (4 disks in raidz1, version 28) in FreeBSD 10.0 (pool was created in 9.1).
Google gives nothing specified :(

Code: 
root@storage:/ # uname -a
FreeBSD storage 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014     root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
root@storage:/ # zpool list
no pools available
root@storage:/ # zpool import
   pool: storage
     id: 10043502052953961628
  state: ONLINE
Assertion failed: (reason == ZPOOL_STATUS_OK), file /usr/src/cddl/sbin/zpool/../../../cddl/contrib/opensolaris/cmd/zpool/zpool_main.c, line 1709.
Abort (core dumped)

root@storage:/ # zdb -l /dev/ada0
--------------------------------------------
LABEL 0
--------------------------------------------
    version: 28
    name: 'storage'
    state: 0
    txg: 3450885
    pool_guid: 10043502052953961628
    hostid: 1989549771
    hostname: 'storage'
    top_guid: 4051799892930199648
    guid: 8630479448589635906
    vdev_children: 1
    vdev_tree:
        type: 'raidz'
...

Core file uploaded. Just in case.
https://mega.co.nz/#!5MwwjaiQ!Yibpdzf7l ... SF8vg_cwA0
 
Re: zpool import - Assertion failed

Silly me.

It imports like this:
Code: 
root@storage:~ # zpool import storage
root@storage:~ # zpool list
NAME      SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
storage  10.9T  7.67T  3.21T    70%  1.00x  ONLINE  -
root@storage:~ #
 
Hi

I get the same behaviour in response to zpool import (without arguments), on FreeBSD 10.0 and 9.3-prerelease14-05-10, but not with 9.2. It lists the zpool name and one of the two disks, then the same "assertion failed" followed by core dump. I haven't tried actually importing the pool, since I would like to know more about the error before I try that. The pool (a two-disk mirror, v5000) was created on 8.4-rc2. I assume that the expected behaviour of zpool import is to list importable pools?

If I physically remove one of the two disks in the pool, zpool import lists the pool (as degraded) successfully and exits cleanly.

Should this be reported as a bug? I would like to sort out what is happening before I proceed with upgrading my NAS.

EDIT: Solved for now. It seems to be fixed in 10.0-STABLE-amd64-20140506. (why is it named "stable" when it is apparently newer than 10.0-RELEASE?)
 
Just as an FYI, the same issue is noted when calling
Code: 
zpool upgrade
. Perhaps a fix will be included in 10.0-RELEASE-p4?
 
You must log in or register to reply here.
Back
Top