-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
crash - maybe dereferenced nullptr - 0.8.0rc4 #8672
Comments
Think this is still an issue with 0.8.2, had three complete lockups. Two last week, one today. Here are the logs:
If you need more information, please let me know. |
I'm currently on 0.8.2-pve2 (proxmox: git )disabled all intensive tasks (Windows backups running inside a VM from one ZFS pool to another) that were causing high-io and the lockups. |
Spoke to early... Today I had the same crash again during high IO...
|
I had the same crash today, same dmesg dump. I think it occured when I set Edit: seems unrelated to |
I think 5ff2249 might have fixed this. Edit: it is definitely fixed by that commit. It is also related to |
I too have |
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. |
this is fixed as commented here: #8672 (comment) |
System information
it's recent a kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/
cmdline is also different (basically disabled meltdown/sprectre mitigations)
no idea if it's related to zfs or an upstream kernel bug or related to the disabled mitigations, I thought I'll leave it here - feel free to close. But could be a deferenced nullpointer?
Describe the problem you're observing
complete hang. load was rising, hung tasks waiting for io - only could do a hard-reset.
Describe how to reproduce the problem
not yet able to reproduce, but machine runs a buildbot and has heavy io.
Include any warning/errors/backtraces from the system logs
last lines before the crash:
The text was updated successfully, but these errors were encountered: