First of all, apologies if this belongs in a different forum. Please advise if I need to move it elsewhere.
Quick summary: I'm running two machines connected by a local network. One running FreeBSD 12.1-p2, the other running FreeNAS-11.3-U1. I have a daily rsync task set up on the FreeNAS machine to push the FreeNAS data disk contents to the FreeBSD machine. When the rsync runs, it gets so far and the destination FreeBSD box crashes.
I have been consulting on the FreeNAS Forum, and this link will provide a few details of the suggestions I received there and some of the things I've tried:
The FreeBSD crash is quite repeatable, and results in a kernel panic of this nature. (The addresses change, which CPU is involved changes, but the general form looks like this):
As discussed on the thread in the FreeNAS forum, I originally was getting an "Unknown error: 122 (122)" in the rsync task log. This proved to be due to corrupted data on the destination pool, but that was cleaned up, but the rsync problem persists. Now the first indication I have of a problem is the notification in the log on the source machine of a broken pipe when the destination machine crashes.
At this point, I'm looking for suggestions for where to look next. Things I've thought of include file size, memory issues, file contents, and file permissions/owner issues. I also updated everything to the latest versions on both FreeBSD and FreeNAS.
Quick summary: I'm running two machines connected by a local network. One running FreeBSD 12.1-p2, the other running FreeNAS-11.3-U1. I have a daily rsync task set up on the FreeNAS machine to push the FreeNAS data disk contents to the FreeBSD machine. When the rsync runs, it gets so far and the destination FreeBSD box crashes.
I have been consulting on the FreeNAS Forum, and this link will provide a few details of the suggestions I received there and some of the things I've tried:
Code:
https://www.ixsystems.com/community/threads/rsync-push-task-causes-kernel-panic-on-freebsd-destination-machine.82965/
The FreeBSD crash is quite repeatable, and results in a kernel panic of this nature. (The addresses change, which CPU is involved changes, but the general form looks like this):
Code:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xfffff80f75d46e00
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff82674048
stack pointer = 0x0:0xfffffe00a0886850
frame pointer = 0x0:0xfffffe00a0886890
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (zio_write_intr_6)
trap number = 12
panic: page fault
cpuid = 0
time = 1583081613
KDB: stack backtrace:
#0 0xffffffff80c1d297 at kdb_backtrace+0x67
#1 0xffffffff80bd05cd at vpanic+0x19d
#2 0xffffffff80bd0423 at panic+0x43
#3 0xffffffff810a7d2c at trap_fatal+0x39c
#4 0xffffffff810a7d79 at trap_pfault+0x49
#5 0xffffffff810a736f at trap+0x29f
#6 0xffffffff81081a0c at calltrap+0x8
#7 0xffffffff82671979 at arc_access+0x109
#8 0xffffffff8267541e at arc_write_done+0x25e
#9 0xffffffff8272b8a1 at zio_done+0x8d1
#10 0xffffffff82726b7c at zio_execute+0xac
#11 0xffffffff80c2fa74 at taskqueue_run_locked+0x154
#12 0xffffffff80c30da8 at taskqueue_thread_loop+0x98
#13 0xffffffff80b90c23 at fork_exit+0x83
#14 0xffffffff81082a4e at fork_trampoline+0xe
Uptime: 23m42s
As discussed on the thread in the FreeNAS forum, I originally was getting an "Unknown error: 122 (122)" in the rsync task log. This proved to be due to corrupted data on the destination pool, but that was cleaned up, but the rsync problem persists. Now the first indication I have of a problem is the notification in the log on the source machine of a broken pipe when the destination machine crashes.
At this point, I'm looking for suggestions for where to look next. Things I've thought of include file size, memory issues, file contents, and file permissions/owner issues. I also updated everything to the latest versions on both FreeBSD and FreeNAS.