Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing past end of object #10211

Closed
hicotton02 opened this issue Apr 15, 2020 · 5 comments
Closed

Accessing past end of object #10211

hicotton02 opened this issue Apr 15, 2020 · 5 comments

Comments

@hicotton02
Copy link

Distribution Name | Slackware
Distribution Version | 14.2
Linux Kernel | 4.19.107-Unraid
Architecture | x64
ZFS Version | 0.8.3-1
SPL Version | 0.8.3-1

Describe the problem you're observing

under heavy load, I get a kernel panic (log below)

Describe how to reproduce the problem

any time that nzbget (docker in Unraid) is downloading at full speed (1GB) for an extended amount of time. can be a few hours up to about a day or so.

Apr 15 10:25:09 Tower kernel: PANIC: zfs: accessing past end of object e26/3da5d (size=6656 access=6244+1043)
Apr 15 10:25:09 Tower kernel: Showing stack for process 31536
Apr 15 10:25:09 Tower kernel: CPU: 32 PID: 31536 Comm: nzbget Tainted: P           O      4.19.107-Unraid #1
Apr 15 10:25:09 Tower kernel: Hardware name: ASUSTeK COMPUTER INC. Z9PE-D16 Series/Z9PE-D16 Series, BIOS 5601 06/11/2015
Apr 15 10:25:09 Tower kernel: Call Trace:
Apr 15 10:25:09 Tower kernel: dump_stack+0x67/0x83
Apr 15 10:25:09 Tower kernel: vcmn_err+0x8b/0xd4 [spl]
Apr 15 10:25:09 Tower kernel: ? __handle_mm_fault+0x8a9/0x11b7
Apr 15 10:25:09 Tower kernel: ? call_function_single_interrupt+0xa/0x20
Apr 15 10:25:09 Tower kernel: ? _cond_resched+0x1b/0x1e
Apr 15 10:25:09 Tower kernel: zfs_panic_recover+0x67/0x7e [zfs]
Apr 15 10:25:09 Tower kernel: ? spl_kmem_zalloc+0xd4/0x107 [spl]
Apr 15 10:25:09 Tower kernel: dmu_buf_hold_array_by_dnode+0x92/0x3b6 [zfs]
Apr 15 10:25:09 Tower kernel: dmu_write_uio_dnode+0x46/0x11d [zfs]
Apr 15 10:25:09 Tower kernel: ? txg_rele_to_quiesce+0x24/0x32 [zfs]
Apr 15 10:25:09 Tower kernel: dmu_write_uio_dbuf+0x48/0x5e [zfs]
Apr 15 10:25:09 Tower kernel: zfs_write+0x6a3/0xbe8 [zfs]
Apr 15 10:25:09 Tower kernel: ? dmu_object_size_from_db+0x1d/0x68 [zfs]
Apr 15 10:25:09 Tower kernel: ? rrw_exit+0x10d/0x11e [zfs]
Apr 15 10:25:09 Tower kernel: zpl_write_common_iovec+0xae/0xef [zfs]
Apr 15 10:25:09 Tower kernel: zpl_iter_write+0xdc/0x10d [zfs]
Apr 15 10:25:09 Tower kernel: do_iter_readv_writev+0x110/0x146
Apr 15 10:25:09 Tower kernel: do_iter_write+0x86/0x15c
Apr 15 10:25:09 Tower kernel: vfs_writev+0x90/0xe2
Apr 15 10:25:09 Tower kernel: ? syscall_trace_enter+0x1d/0x1aa
Apr 15 10:25:09 Tower kernel: ? syscall_trace_enter+0x163/0x1aa
Apr 15 10:25:09 Tower kernel: do_writev+0x6b/0xe2
Apr 15 10:25:09 Tower kernel: do_syscall_64+0x57/0xf2
Apr 15 10:25:09 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 15 10:25:09 Tower kernel: RIP: 0033:0x14d8bf345f90
Apr 15 10:25:09 Tower kernel: Code: 89 74 24 10 48 89 e5 48 89 04 24 49 29 c6 48 89 54 24 18 4c 89 74 24 08 49 01 d6 48 63 7b 78 49 63 d7 4c 89 e8 48 89 ee 0f 05 <48> 89 c7 e8 1b 85 fd ff 49 39 c6 75 19 48 8b 43 58 48 8b 53 60 48
Apr 15 10:25:09 Tower kernel: RSP: 002b:000014d8bec4ea90 EFLAGS: 00000212 ORIG_RAX: 0000000000000014
Apr 15 10:25:09 Tower kernel: RAX: ffffffffffffffda RBX: 0000564ba7effb40 RCX: 000014d8bf345f90
Apr 15 10:25:09 Tower kernel: RDX: 0000000000000002 RSI: 000014d8bec4ea90 RDI: 000000000000003c
Apr 15 10:25:09 Tower kernel: RBP: 000014d8bec4ea90 R08: 0000000000000001 R09: 000014d8bf38f873
Apr 15 10:25:09 Tower kernel: R10: 0000000000000000 R11: 0000000000000212 R12: 0000000000000018
Apr 15 10:25:09 Tower kernel: R13: 0000000000000014 R14: 0000000000000413 R15: 0000000000000002
@gmelikov
Copy link
Member

Duplicate of #8673 , should be fixed by #10148 , you may try it if you're ready to compile ZFS with it, or just wait for next release.

@hicotton02
Copy link
Author

hicotton02 commented Apr 15, 2020

The version that I am running should include that fix. is there a way to verify? the version I am running was built from https://github.com/openzfs/zfs/tree/7e3df9db128722143734a9459771365ea19c1c40
and I am under the assumption that it includes #10148

@gmelikov
Copy link
Member

@hicotton02 you've specified 0.8.3 release, it's not included in it. Can you clarify this moment? And please show cat /sys/module/zfs/version

@hicotton02
Copy link
Author

I apologize for any miscommunication, zfs is added via plugin to Unraid here:
https://forums.unraid.net/topic/41333-zfs-plugin-for-unraid/?do=findComment&comment=842464

The owner posted that he compiled what I mentioned earlier.

Linux 4.19.107-Unraid.
Last login: Wed Apr 15 13:35:20 -0700 2020 on /dev/pts/7.
root@Tower:~# cat /sys/module/zfs/version
0.8.3-1

@hicotton02
Copy link
Author

I think i found the issue. the plugin is being reverted back to the previous version on reboot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants