-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Another deadlock with zfs 0.6.4-1 on CentOS 7 #3350
Comments
@deajan All the processes you show are blocked on a superblock's znodes lock. See #3308 for a bit of rationale as to why they shouldn't even be doing this. You've unfortunately got a kernel version on which the referenced callback is actually enabled. I have a feeling the triggering event is the rollback you mentioned since that can cause the lock to be taken in other places, none of which appear to be shown in your list of blocked processes. |
@dweeezil Thanks for the background :) Note for my future me:
|
In order to close this old bug report, I've retried these commands today on the same system with zfs 0.6.5.7. |
Hello,
I have a production backup server which just happened to have a deadlock with the latest zfs release.
Here's the info i can provide:
I have a cron task that writes memory and arc stats every 3 minutes to a file.
Here are the results and of course the kernel crash
Kernel dump: https://gist.github.com/deajan/fe7c9b6be3c267d21d8c
Stats some minutes before the crash (mon. april 27 11:03:01 CEST 2015):
When the crash happened, there was a backup running over SMB and i was rolling back a snapshot.
Anything else i can provide ?
The text was updated successfully, but these errors were encountered: