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

panic, panic on boot, panic on connection of drive #101

Open
GoogleCodeExporter opened this issue Apr 2, 2015 · 2 comments
Open

panic, panic on boot, panic on connection of drive #101

GoogleCodeExporter opened this issue Apr 2, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.zfs -b 32k -V 20gb pool/tst
2.zfs list 
3.

What is the expected output? What do you see instead?
no panics, 


What version of the product are you using? On what operating system?
10.6.8


Please provide any additional information below.
external JOBD, raidz2
I have to move the zfs.kext to connect the drives without a panic.

Original issue reported on code.google.com by [email protected] on 11 Nov 2011 at 9:34

@GoogleCodeExporter
Copy link
Author

Did you try creating your ZFS with default parameters?  Such as 'zfs create 
pool/test'.  Did you boot another operating system, such as a Fedora liveusb 
with 'sudo yum install zfs-fuse', to see if the zpool will mount?

Original comment by [email protected] on 19 Nov 2011 at 11:47

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I have other filesystems on that zpool which work fine.  I tryed the volumes 
create just to test it. Silly me for doing it on a pool I needed.  Being a 
programmer I rebuilt the kext with zvol_get_stats disabled and was able to load 
the zpool.  Tried to destroy the test volume and that failed. Ran zfs with the 
debugger and skipped a failing test and was able to destroy the test volume.  I 
am assuming that the zvol was partly created leaving the zpool in an 
inconsistent state.  THe zpool seems ok now.  I plan to investigate more later 
in a safer environment.

Original comment by [email protected] on 20 Nov 2011 at 4:00

  • Added labels: ****
  • Removed labels: ****

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

No branches or pull requests

1 participant