panic[cpu3]/thread=fffffe0010006c20: assertion failed: rrd->bytes_read >= rwa->bytes_read (0x3e20 >= 0xfffffffffffe3ce8), file: ../../common/fs/zfs/dmu_recv.c, line: 2472

[ikozhukhov]

panic with ZTS in loop on random circle.

System information

Type	Version/Name
Distribution Name	DilOS
Distribution Version
Linux Kernel
Architecture
ZFS Version
SPL Version

Describe the problem you're observing

run ZTS in look on jenkins and on several tries in panic dump with content:

panic[cpu3]/thread=fffffe0010006c20: assertion failed: rrd->bytes_read >= rwa->bytes_read (0x3e20 >= 0xfffffffffffe3ce8), file: ../../common/fs/zfs/dmu_recv.c, line: 2472

fffffe0010006b80 genunix:process_type+19b089 ()
fffffe0010006bc0 zfs:receive_process_record+60 ()
fffffe0010006c00 zfs:receive_writer_thread+7d ()
fffffe0010006c10 unix:thread_start+8 ()

panic: entering debugger (continue to save dump)

Welcome to kmdb
kmdb: unable to determine terminal type: assuming `vt100'
Loaded modules: [ scsi_vhci crypto mac cpc uppc mr_sas neti sd ptm ufs unix mpt zfs krtld ipc sata apix uhci pmcs hook genunix idm ip logindmux usba xhci specfs pcplusmp nfs random mm cpu.generic arp mpt_sas sockfs ]
[3]> ::spa -v
ADDR                 STATE NAME
fffffe0be8cae000    ACTIVE rpool

    ADDR             STATE     AUX          DESCRIPTION
    fffffe0be8dc2000 HEALTHY   -            root
    fffffe0be8dc7000 HEALTHY   -              /dev/dsk/c1t0d0s0
fffffe93e3c58000    ACTIVE testpool

    fffffe93e3c84000 HEALTHY   -            root
    fffffe93e3c89000 HEALTHY   -              /dev/dsk/c0t600144F0A2C9046800005D21E0E50001d0s0
[3]> $C
fffffffffbca0420 kmdb_enter+0xb()
fffffffffbca0450 debug_enter+0x53(fffffffffb9a2480)
fffffffffbca0530 panicsys+0x545(fffffffffbf97f38, fffffe0010006a98, fffffffffbca0540, 1)
fffffe0010006a80 vpanic+0x15c()
fffffe0010006af0 0xfffffffffb8b7dd1()
fffffe0010006b80 0xfffffffffbe43711()
fffffe0010006bc0 zfs`receive_process_record+0x60(fffffe46ed7695c0, fffffe4701c1f740)
fffffe0010006c00 zfs`receive_writer_thread+0x7d(fffffe46ed7695c0)
fffffe0010006c10 thread_start+8()
[3]>

tests log:

04:53:26.581 Test: /opt/zfs-tests/tests/functional/refquota/setup.ksh (run as root) [00:00] [PASS]
04:53:34.365 Test: /opt/zfs-tests/tests/functional/refquota/refquota_001_pos.ksh (run as root) [00:07] [PASS]
04:53:43.309 Test: /opt/zfs-tests/tests/functional/refquota/refquota_002_pos.ksh (run as root) [00:08] [PASS]
04:53:50.595 Test: /opt/zfs-tests/tests/functional/refquota/refquota_003_pos.ksh (run as root) [00:07] [PASS]
04:53:57.700 Test: /opt/zfs-tests/tests/functional/refquota/refquota_004_pos.ksh (run as root) [00:07] [PASS]
04:54:03.541 Test: /opt/zfs-tests/tests/functional/refquota/refquota_005_pos.ksh (run as root) [00:05] [PASS]
04:54:04.871 Test: /opt/zfs-tests/tests/functional/refquota/refquota_006_neg.ksh (run as root) [00:01] [PASS]
04:54:05.732 Test: /opt/zfs-tests/tests/functional/refquota/refquota_007_neg.ksh (run as root) [00:00] [PASS]
05:15:12.821 FATAL: command execution failed

panic on next test.

Describe how to reproduce the problem

Include any warning/errors/backtraces from the system logs

[ikozhukhov]

@behlendorf @ahrens

[behlendorf]

Duplicate of #9067.

[stale]

This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.