-
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
Kernel panic in dmu_write() on i686 #1284
Comments
Crash happened while browsing. |
Thank we'll want to dig in to this when we have the time. Was this was a one time event? |
I moved data to zfs, and after a couple of days, that happened, but after that moved again to ext4. |
OK, well we'll leave the issue open for reference in case someone else hits something similar. This however is the first report I've heard of something like this. |
Looks similar:
was compiling kernel. System was still working, and operational on different file systems. doing
machine have 2GB of ram. I can repeat this error quite reliably. |
I will build debug kernel (not sure how, when I have sources on zfs itself... will need to clone/download again) and see if it will show any more interesting infos. |
This looks like an issue in the current mmap() code. I am doing a rewrite that will replace all of the code involved in this backtrace. It should fix this when it is done. |
@baryluk You might be able to catch the cause if this issue if you rebuild the spl and zfs with --enable-debug and you encounter a build failure. |
This was almost certainly addressed by the various mmap improvements and bug fixes over the last 18 months. Since there are no recent similar reports I'm closing this as stale. |
Screenshot
Rebooted the machine with sysrq b
The text was updated successfully, but these errors were encountered: