I'm getting the following assertion failure when using my zfs-crypto
bits:
panic[cpu0]/thread=2a100c8dcc0: assertion failed: vdev_config_sync(rvd,
txg) == 0, file: ../../common/fs/zfs/spa.c, line: 2149
000002a100c8d890 genunix:assfail+7c (7ae6e9c8, 7ae6e9e8, 865, 1853c00,
12b4000, 0)
%l0-3: 0000000070212458 00000600009d3680 00000600009d3810
0000000000000000
%l4-7: 0000000000000081 0000000000000000 0000000001899000
0000000000000000
000002a100c8d940 zfs:spa_sync+1dc (600009d3680, 151, 6000119edc0,
6000119edc0, 7ae59800, 7ae6e800)
%l0-3: 00000600009d3810 00000600009d37d8 0000030027c8c168
0000030027c8c138
%l4-7: 0000030027fe50c0 00000600009d3848 0000030027c8c000
0000000070212000
000002a100c8d9f0 zfs:txg_sync_thread+1a4 (30027c8c000, 151, 2a100c8dab0,
30027c8c120, 30027c8c112, 30027c8c110)
%l0-3: 0000000000000000 0000030027c8c0d0 0000030027c8c0d8
0000030027c8c116
%l4-7: 0000030027c8c114 0000030027c8c0c8 0000000070212094
000000007ae59f78
These are a slightly updated version of what I posted on the project
website for being in sync with onnv_40. For those internal to Sun you
can see the webrev here:
http://borg.sfbay/cube/projects/zfs-crypto/webrev/
The dump for those internal is on mix.sfbay in the usual place (dump
number 8).
For those external sorry you'll need to live with the attached diff
output just now.
I came to the conclusion that I needed to change the on disk version
number for crypto since older releases would panic if they saw the crypt
flag turned on in the blkptr_t. The above panic came seconds after
zpool upgrade had said it was complete.
I must be missing something silly any help much appreciated.
--
Darren J Moffat
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: diffs.current
URL:
<http://mail.opensolaris.org/pipermail/zfs-code/attachments/20060517/99ab04e7/attachment.ksh>
