Odd import messages or errors?

[aufalien]

I thought to post a Quicktime as a picture is worth a thousand words. I'm seeing odd messages that I can't really articulate.

Something about best uber block and using txg etc....

Normally doing the boot process while an import is being performed, I'm used to a very clean output w/o issue.

However you'll notice ~1 minute in that some really weird messages show up while importing my pool named void.

At any rate the import does complete but the messages seem alarming.

Brief system specs;
Supermicro X10DRi-LN4+
Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
128GB RAM
SAS3 9300-4i4e HBA
5x 12 disk Supermicro SAS3 JBODS
60x 8TB Seagate Enterprise configured as a single pool of 10x RaidZ2 vdevs
12.0-U6
No L2ARC or SLOG devices
Async
NFSv3 only serving home directories, assets, videos/media and other mostly read data
Solarflare dual 10Gb fiber, standard frame, non jumbo

Here is my Quicktime;

systemboot.mov

drive.google.com

 

[aufalien]

The reason for my post is that this server crash/boots.

I have the crash logs but below are the last messages before reboot;

panic.txt;
Solaris(panic): zfs: accessing past end of object 3ef/2303667 (size=230400 access=230080+16432)

msgbuf.txt (just the relevant parts);
<6>pid 1497 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)
panic: Solaris(panic): zfs: accessing past end of object 3ef/2303667 (size=230400 access=230080+16432)
cpuid = 38
time = 1633552421
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe017b570500
vpanic() at vpanic+0x17b/frame 0xfffffe017b570550
panic() at panic+0x43/frame 0xfffffe017b5705b0
vcmn_err() at vcmn_err+0xcd/frame 0xfffffe017b5706e0
zfs_panic_recover() at zfs_panic_recover+0x59/frame 0xfffffe017b570740
dmu_buf_hold_array_by_dnode() at dmu_buf_hold_array_by_dnode+0x96/frame 0xfffffe017b5707c0
dmu_write_uio_dnode() at dmu_write_uio_dnode+0x3a/frame 0xfffffe017b570840
dmu_write_uio_dbuf() at dmu_write_uio_dbuf+0x42/frame 0xfffffe017b570870
zfs_write() at zfs_write+0x6e4/frame 0xfffffe017b570a30
VOP_WRITE_APV() at VOP_WRITE_APV+0xeb/frame 0xfffffe017b570b40
nfsvno_write() at nfsvno_write+0x184/frame 0xfffffe017b570bf0
nfsrvd_write() at nfsrvd_write+0x532/frame 0xfffffe017b570f40
nfsrvd_dorpc() at nfsrvd_dorpc+0x652/frame 0xfffffe017b571110
nfssvc_program() at nfssvc_program+0x5d3/frame 0xfffffe017b5712e0
svc_run_internal() at svc_run_internal+0x98e/frame 0xfffffe017b571420
svc_run() at svc_run+0x1ba/frame 0xfffffe017b571470
nfsrvd_nfsd() at nfsrvd_nfsd+0x311/frame 0xfffffe017b5715d0
nfssvc_nfsd() at nfssvc_nfsd+0x55a/frame 0xfffffe017b571aa0
sys_nfssvc() at sys_nfssvc+0xb6/frame 0xfffffe017b571ac0
amd64_syscall() at amd64_syscall+0x387/frame 0xfffffe017b571bf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe017b571bf0
--- syscall (155, FreeBSD ELF64, sys_nfssvc), rip = 0x8002e1b2a, rsp = 0x7fffffffe578, rbp = 0x7fffffffe810 ---
KDB: enter: panic


I don't speak boink so hoping some one can decipher?

 

[aufalien]

Based on this link which seems identical to my issue, I went ahead and submitted a bug report;

PANIC: zfs: accessing past end of object bf37/35f70 · Issue #8673 · openzfs/zfs

System information Type Version/Name Distribution Name Debian Distribution Version 9.7 Linux Kernel 4.15.18 Architecture x64 ZFS Version 0.7.12-1 SPL Version 0.7.12-1 Describe the problem you're ob...

github.com

My bug report below. Oddly enough I set it to high but it submitted as low. Obviously this is VERY high.

https://jira.ixsystems.com/browse/NAS-112704

 

[aufalien]

I've included a truncated log file for brevity showing the odd import messages upon boot.

Could be benign but I've not seen them before.