On Apr 28, 2011, at 5:04 PM, Stephan Budach wrote: > Am 28.04.11 11:51, schrieb Markus Kovero: >>> failed: space_map_load(sm, zfs_metaslab_ops, SM_FREE, smo, >>> spa->spa_meta_objset) == 0, file ../zdb.c, line 571, function dump_metaslab >>> Is this something I should worry about? >>> uname -a >>> SunOS E55000 5.11 oi_148 i86pc i386 i86pc Solaris >> I thought we were talking about solaris 11 express, not oi? >> Anyway, no idea about how openindiana should work or not. >> >> Yours >> Markus Kovero >> _______________________________________________ > Maybe this hasn't anything to do with Sol11Expr vs. oi. I do get the same > error on one of my Sol11Expr hosts, when I run it against a 50 TB zpool: > > root@solaris11a:~# uname -a > SunOS solaris11a 5.11 snv_151a i86pc i386 i86pc > > root@solaris11a:~# /usr/sbin/amd64/zdb -mm backupPool_01 > /tmp/zdb-mm.out > Assertion failed: space_map_load(sm, zfs_metaslab_ops, SM_FREE, smo, > spa->spa_meta_objset) == 0, file ../zdb.c, line 593, function dump_metaslab
zdb is not intended to be run against changing pools/datasets. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
