Details
-
Type:
Bug
-
Status: Engineering Closed (View Workflow)
-
Priority:
Low
-
Resolution: Duplicate
-
Affects Version/s: 12.0-U1
-
Fix Version/s: N/A
-
Component/s: OS
-
Labels:
Description
I've recently built a new system running the latest TrueNAS version 12.0u1 within an Hypver-V (win 2019 with latest patches) hypervisor.
TrueNAS behaved well until today when I actually started putting some load on the system by moving files (3TBs in total) from another FreeNAS system to the new TrueNAS system between iSCSI targets both mounted on a Win 2019 server. After some time (30 minutes or so) the target TrueNAS system panicked with the below trace. The iSCSI target is a zvol within an encrypted pool.
panic: VERIFY3(0 == spa_do_crypt_abd(B_TRUE, spa, &zio->io_bookmark, BP_GET_TYPE(bp), BP_GET_DEDUP(bp), BP_SHOULD_BYTESWAP(bp), salt, iv, mac, psize, zio->io_abd, eabd, &no_crypt)) failed (0 == 5)
cpuid = 2
time = 1608621095
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00e90cc890
vpanic() at vpanic+0x17b/frame 0xfffffe00e90cc8e0
spl_panic() at spl_panic+0x3a/frame 0xfffffe00e90cc940
zio_encrypt() at zio_encrypt+0x543/frame 0xfffffe00e90cc9d0
zio_execute() at zio_execute+0x6a/frame 0xfffffe00e90cca20
taskqueue_run_locked() at taskqueue_run_locked+0x144/frame 0xfffffe00e90cca80
taskqueue_thread_loop() at taskqueue_thread_loop+0xb6/frame 0xfffffe00e90ccab0
fork_exit() at fork_exit+0x7e/frame 0xfffffe00e90ccaf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00e90ccaf0