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.

Sign up for GitHub

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

Jump to bottom

Hard kernel crash during zfs send on Ubuntu 12.04 64-bit using stable PPA #882

Closed
robinsmidsrod opened this issue Aug 22, 2012 · 4 comments
Closed

Hard kernel crash during zfs send on Ubuntu 12.04 64-bit using stable PPA #882

robinsmidsrod opened this issue Aug 22, 2012 · 4 comments
Milestone
0.6.0-rc11

Comments

@robinsmidsrod
Copy link

I was doing a zfs send (approx. 15GB) from a raidz zpool to /dev/null when I got this kernel panic. Machine was completely hung and I was only able to get the panic message by taking a picture of the screen.

The picture is here: https://dl.dropbox.com/u/354628/ZFSonLinux%20kernel%20panic%20on%20Ubuntu%2012.04%20%2064-bit%20%28Robin%20Smidsr%C3%B8d%2C%202012%29.jpg

DeHackEd on IRC suggested that I should look for zio_done-related issues, but I wasn't able to figure out if any of the ones that popped up was similar to mine.

Kernel version: 3.2.0.29-generic #46-Ubuntu

Keywords: z_rd_int/0 zio_done zio_remove_child zio_execute cv_broadcast taskq_thread task_done __ticket_spin_lock _raw_spin_lock mutex_lock NMI EOE
@behlendorf
Copy link
Contributor

Was this a one time event or have you been able to reproduce it?

@robinsmidsrod
Copy link
Author

I have only seen it once, but the machine it happened on is for testing ZFS, and it's been off since this incident. I haven't tried to reproduce it, but I'll try it again and see if it happens again. I'll report back as soon as I can with the results.

@robinsmidsrod
Copy link
Author

I tried reproducing the problem on the same hardware with the same setup. I was unable to reproduce the problem. I was still running the same versions of all software.

@behlendorf
Copy link
Contributor

There's not really enough in the picture to explain what happened here. I'm going to close this issue due to lack of information, but if you see anything else strange please open a new issue and we'll debug it there.

@dbourget dbourget mentioned this issue Dec 14, 2013
Closed
pcd1193182 pushed a commit to pcd1193182/zfs that referenced this issue Sep 26, 2023
@ahrens
Switch from Rusoto to AWS S3 SDK. (openzfs#882)
ad9380a 
This required extensive changes to `object_access::s3`.  I took advantage of
this to clean up as much as I could in s3.rs.

We use the SDK's timeout and retry-on-failure for ListObjects operations, which
lets us easily use the sdk's pagination.  For other operations, we implement
the timeout and retry-on-failure, as we did before.  However, we use the SDK's
error classification code to determine which errors are retryable.  By using
our own retry code, we have more precise control and can ensure that we retry
forever (on retryable errors) even when under a heavy load.

This change adds support for IMDSv2, which is provided by the AWS SDK.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.6.0-rc11
Development

No branches or pull requests
2 participants
@robinsmidsrod @behlendorf