-
Notifications
You must be signed in to change notification settings - Fork 20
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
BSOD on zpool import #428
Comments
I have seen the |
Win 11 24H2 26100.2894, OpenZFSOnWindows-debug-2.2.6rc11.exe
Then I'm trying to import my dataset "Test": Also minidump contains the following:
Any ideas please? @lundman should I give some more information for debugging the problem? |
This heap corruption (also mentioned in #417) makes (at least) the 2.2.6rc* almost unusable here. The kernel stack trace is not stable, but often ends up in Windows Driver Frameworks (wdf01000.sys) |
Could you please give me instructions how to do it? Thank you! |
One sec, currently building something to see if we can fix it, but nothing is working on my build VM today, so I have been shaving yaks all morning |
Took a bit, it highlighted a couple of bugs, which blocked unmounts, so maybe that is a good thing. https://github.com/openzfsonwindows/openzfs/releases/tag/zfswin-2.3.0rc1 |
Running into heap corruption in wdf01000.sys - immediately on installing and then on every boot. Had to remove the driver manually to break boot loop. |
Did you keep a MEMORY.DMP from one of those wdf01000.sys BSODs? |
Yes. What can I extract to help you? |
Gimme stack at least, so we can get a feel for the issue. |
At
This was during installation - a couple of bytes (220h) before that there is
as is 260h bytes after that. At ffffa7816e100340 there is
Anything looks familiar? |
Hmmm not particularly familiar. The It could be interesting check if |
Forgot to add that this BSOD was the one during installation. Wasn't able to capture the subsequent ones on boot yet. Here's
I've got another one on install. It looks the same but manages to |
Interesting. OK so we expect |
System information
Describe the problem you're observing
BSOD on trying to import pool (every time)
Describe how to reproduce the problem
zpool import testpool
Include any warning/errors/backtraces from the system logs
The failing assert is
VERIFY(vp->v_usecount > 0) failed.
at
C:\src\openzfs\module\os\windows\spl\spl-vnode.c:1407
The text was updated successfully, but these errors were encountered: