Hi All,
here is an other kind of kernel panic caused by ZFS that we found.
I have dumps if needed.
#zpool import
pool: zpool8
id: 7382567111495567914
state: ONLINE
status: The pool is formatted using an older on-disk version.
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:
volume8 ONLINE
c0t60001FE100118DB00009119074440055d0 ONLINE
#zpool import zpool8
Apr 7 22:53:34 SERVER140 ^Mpanic[cpu1]/thread=ffffff001807dc80:
Apr 7 22:53:34 SERVER140 genunix: [ID 361072 kern.notice] zfs: freeing free
segment (offset=17712545792 size=131072)
Apr 7 22:53:34 SERVER140 unix: [ID 100000 kern.notice]
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d380
genunix:vcmn_err+28 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d470
zfs:zfs_panic_recover+b6 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d500
zfs:space_map_remove+147 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d5a0
zfs:space_map_load+1f4 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d5e0
zfs:metaslab_activate+66 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d6a0
zfs:metaslab_group_alloc+1fb ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d770
zfs:metaslab_alloc_dva+17d ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d810
zfs:metaslab_alloc+6f ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d850
zfs:zio_dva_allocate+63 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d870
zfs:zio_next_stage+b3 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d8a0
zfs:zio_checksum_generate+6e ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d8c0
zfs:zio_next_stage+b3 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d930
zfs:zio_write_compress+202 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d950
zfs:zio_next_stage+b3 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d9a0
zfs:zio_wait_for_children+5d ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d9c0
zfs:zio_wait_children_ready+20 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d9e0
zfs:zio_next_stage_async+bb ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807da00
zfs:zio_nowait+11 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807da80
zfs:dmu_objset_sync+180 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dad0
zfs:dsl_dataset_sync+42 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807db40
zfs:dsl_pool_sync+a7 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dbd0
zfs:spa_sync+1c5 ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dc60
zfs:txg_sync_thread+19a ()
Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dc70
unix:thread_start+8 ()
Apr 7 22:53:34 SERVER140 unix: [ID 100000 kern.notice]
Apr 7 22:53:34 SERVER140 genunix: [ID 672855 kern.notice] syncing file
systems...
Apr 7 22:53:35 SERVER140 genunix: [ID 904073 kern.notice] done
Apr 7 22:53:36 SERVER140 genunix: [ID 111219 kern.notice] dumping to
/dev/dsk/c2t0d0s3, offset 1677983744, content: kernel
Apr 7 22:54:04 SERVER140 genunix: [ID 409368 kern.notice] ^M100% done: 644612
pages dumped, compression ratio 4.30,
Apr 7 22:54:04 SERVER140 genunix: [ID 851671 kern.notice] dump succeeded
gino
This message posted from opensolaris.org
Gino, Were you able to recover by setting zfs_recover? Thanks, George Gino wrote:> Hi All, > here is an other kind of kernel panic caused by ZFS that we found. > I have dumps if needed. > > > #zpool import > > pool: zpool8 > id: 7382567111495567914 > state: ONLINE > status: The pool is formatted using an older on-disk version. > 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: > > volume8 ONLINE > c0t60001FE100118DB00009119074440055d0 ONLINE > > > #zpool import zpool8 > > > > Apr 7 22:53:34 SERVER140 ^Mpanic[cpu1]/thread=ffffff001807dc80: > Apr 7 22:53:34 SERVER140 genunix: [ID 361072 kern.notice] zfs: freeing free segment (offset=17712545792 size=131072) > Apr 7 22:53:34 SERVER140 unix: [ID 100000 kern.notice] > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d380 genunix:vcmn_err+28 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d470 zfs:zfs_panic_recover+b6 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d500 zfs:space_map_remove+147 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d5a0 zfs:space_map_load+1f4 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d5e0 zfs:metaslab_activate+66 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d6a0 zfs:metaslab_group_alloc+1fb () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d770 zfs:metaslab_alloc_dva+17d () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d810 zfs:metaslab_alloc+6f () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d850 zfs:zio_dva_allocate+63 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d870 zfs:zio_next_stage+b3 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d8a0 zfs:zio_checksum_generate+6e () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d8c0 zfs:zio_next_stage+b3 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d930 zfs:zio_write_compress+202 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d950 zfs:zio_next_stage+b3 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d9a0 zfs:zio_wait_for_children+5d () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d9c0 zfs:zio_wait_children_ready+20 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807d9e0 zfs:zio_next_stage_async+bb () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807da00 zfs:zio_nowait+11 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807da80 zfs:dmu_objset_sync+180 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dad0 zfs:dsl_dataset_sync+42 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807db40 zfs:dsl_pool_sync+a7 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dbd0 zfs:spa_sync+1c5 () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dc60 zfs:txg_sync_thread+19a () > Apr 7 22:53:34 SERVER140 genunix: [ID 655072 kern.notice] ffffff001807dc70 unix:thread_start+8 () > Apr 7 22:53:34 SERVER140 unix: [ID 100000 kern.notice] > Apr 7 22:53:34 SERVER140 genunix: [ID 672855 kern.notice] syncing file systems... > Apr 7 22:53:35 SERVER140 genunix: [ID 904073 kern.notice] done > Apr 7 22:53:36 SERVER140 genunix: [ID 111219 kern.notice] dumping to /dev/dsk/c2t0d0s3, offset 1677983744, content: kernel > Apr 7 22:54:04 SERVER140 genunix: [ID 409368 kern.notice] ^M100% done: 644612 pages dumped, compression ratio 4.30, > Apr 7 22:54:04 SERVER140 genunix: [ID 851671 kern.notice] dump succeeded > > gino > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
> Gino, > > Were you able to recover by setting zfs_recover? >Unfortunately no :( Using zfs_recover not allowed us to recover any of the 5 corrupted zpool we had .. Please note that we lost this pool after a panic caused by trying to import a corrupted zpool! tnx, gino This message posted from opensolaris.org