-
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
0.7.0-rc3 kernel lockups when running bonnie++ benchmark #5932
Labels
Type: Regression
Indicates a functional regression
Milestone
Comments
SenH
changed the title
0.7.0-rc3 kernel lockups
0.7.0-rc3 kernel lockups when running bonnie++ benchmark
Mar 27, 2017
The offset in - bcopy((char *)zio->io_data + start - io_start,
- ve->ve_data + start - ve->ve_offset, end - start);
+ abd_copy_off(ve->ve_abd, zio->io_abd, start - io_start,
+ start - ve->ve_offset, end - start); |
11 tasks
@SenH this has been fixed in master. |
behlendorf
pushed a commit
to LLNL/zfs
that referenced
this issue
Mar 28, 2017
The offset arguments is wrong when changing to abd_copy_off in a6255b7 Reviewed-by: George Melikov <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Gvozden Neskovic <[email protected]> Signed-off-by: Chunwei Chen <[email protected]> Closes openzfs#5932 Closes openzfs#5936
Thanks for looking into it and fixing this so fast. Several runs of bonnie++ seem to complete without my kernel locking up. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Describe the problem you're observing
After installing 0.7.0-rc3, my system consequently locks ups during a bonnie++ benchmark. All ZFS commands hang, only solution is to power cycle the system. Since this system is my home NAS I did not investigate further and rolled back to 0.6.5.9. I can provide the full syslog (which repeats the lockup messages until reboot) if necessary.
The bonnie benchmark completes successfully in 0.6.5.9.
Describe how to reproduce the problem
bonnie++ -f -b -s 16G:1048576 -n 0 -d /mnt/tank
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: