Skip to content
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

destroy freshly created pool cause BSOD on windows 10 #162

Closed
Musickiller opened this issue Oct 6, 2022 · 2 comments
Closed

destroy freshly created pool cause BSOD on windows 10 #162

Musickiller opened this issue Oct 6, 2022 · 2 comments

Comments

@Musickiller
Copy link

System information

Type Version/Name
Distribution Name Windows
Distribution Version 10
Kernel Version
Architecture x64
OpenZFS Version OpenZFSOnWindows-debug-2.1.99-1005-g5d39a0e3d-dirty (zfs-2.0.0-2)

Describe the problem you're observing

After a pool is created as in here (#7 (comment)), I've called "destroy" (wanted to change creation parameters), which caused BSOD

Describe how to reproduce the problem

fsutil file createnew D:\poolfile.bin 500000000
zpool create daddy \\?\D:\poolfile.bin
zpool status
destroy daddy

Include any warning/errors/backtraces from the system logs

please tell me where to find logs 👶

last thing I have seen in the console was something like zfsunmount for a briefest of moments

note for myself: crash happened at about 2022-10-06 17:10

@andrewc12
Copy link

Hi, I beleive we've fixed some crashes related to unmounting since that version of the driver, so you might want to use a newer version of the fully signed driver from here https://openzfsonosx.org/wiki/Windows_builds

The newest one actually came out today.

@Musickiller
Copy link
Author

this one was fast! I confirm this solved =D 🥳👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants