-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
PANIC at arc.c:6120:arc_release(), VERIFY(HDR_EMPTY(hdr)) failed #9897
Comments
Just got it again. If it helps, I have two pools; two mirrored 12TB SATA drives and two mirrored 1TB SSDs (one NVMe, one SATA). If anyone has any patch/workaround/diagnostics/tests they want me to try, let me know; I would be glad to help troubleshoot this.
|
I can reliably reproduce it -- by hitting Control-S (save keybind) in my Sublime Text 3 session as rapidly as possible (about 2 times per second or so for a few seconds).
|
This looks very similar to a panic observed on FreeBSD, I've filed a FreeBSD PR at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245683 too. |
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 issue has not been observed recently, however it hasn't been specifically addressed either so it's likely not stale. |
I wonder if the In arc_release, we basically have:
So in short, we asserted |
Unfortunately, there was an overzealous assertion that was (in pretty specific circumstances) false, causing failure. Let's not, and say we did. Closes: openzfs#9897 Closes: openzfs#12020 Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Unfortunately, there was an overzealous assertion that was (in pretty specific circumstances) false, causing failure. This assertion was added in error, so we're removing it. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <gwilson@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Rich Ercolani <rincebrain@gmail.com> Closes openzfs#9897 Closes openzfs#12020 Closes openzfs#12246
Unfortunately, there was an overzealous assertion that was (in pretty specific circumstances) false, causing failure. This assertion was added in error, so we're removing it. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <gwilson@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Rich Ercolani <rincebrain@gmail.com> Closes openzfs#9897 Closes openzfs#12020 Closes openzfs#12246
Unfortunately, there was an overzealous assertion that was (in pretty specific circumstances) false, causing failure. This assertion was added in error, so we're removing it. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <gwilson@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Rich Ercolani <rincebrain@gmail.com> Closes openzfs#9897 Closes openzfs#12020 Closes openzfs#12246
Unfortunately, there was an overzealous assertion that was (in pretty specific circumstances) false, causing failure. This assertion was added in error, so we're removing it. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: George Wilson <gwilson@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Rich Ercolani <rincebrain@gmail.com> Closes openzfs#9897 Closes openzfs#12020 Closes openzfs#12246
System information
Describe the problem you're observing
I was saving a file in Sublime Text, and ST3 froze and the aforementioned text showed up in dmesg. The system was unusable, I had to use magic-sysrq to halt it.
Describe how to reproduce the problem
This is the first time I encountered this problem and I am unable to reproduce it. For what it's worth, I compiled ZFS with --enable-debug --enable-debuginfo --enable-debug-kmem
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: