-
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
__cv_destroy()) ASSERTION(cvp->cv_mutex == NULL) #943
Comments
I've seen this error a few times now, and I thought we already had an issue open on it, but I can't find it now. According to the ASSERT there is a process using the condition variable when it is being destroyed. This is very similar to issue #47 which was fixed. If your able to consistently reproduce this we can put together a debugging patch. I suspect there is just a very tight race here in the cv implementation we need to fix. |
@smallma Can you please apply the above debugging patch to the SPL. It should give us a little more insight in to what's going wrong. It also closes one small race so it might fix the issue. We'll have to see. |
Thanks, I'll try it :) |
There still appears to be a race in the condition variables where ->cv_mutex is set after we are woken from the cv_destroy wait queue. This might be possible when cv_destroy() is called immediately after cv_broadcast(). We had some troubles with this previously but there may still be a small race, see commit d599e4f. The following patch closes one small race and improves the ASSERTs such that they log the offending value. Signed-off-by: Brian Behlendorf <[email protected]> openzfs/zfs#943
Hello behlendorf, Sep 20 18:03:57 Qmulus-60eb69d22812 kernel: : [248650.654854] INFO: task zfs:27935 blocked for more than 120 seconds. |
This is just an advisory warning about a thread which was blocked for longer than usual. It's not harmful. |
Thanks. :) I used "ps -eo wchan:30,comm,s|grep -w D" command to check why zpool hang up and found many in D as below. Do you know how to solve it? Thanks. cv_wait_common zfs D |
If your not hitting the above ASSERT then there doesn't appear to be anything wrong. Does the pool appear to be hung in some way? |
This time I am not hitting ASSERT problem. but there are a lot of warning message occurred. When I execute zfs list or zpool status, the console has got stuck. And I can't write anything to zfs mountpoint. Do you know how to trace it? Thanks. By the way, I tried this patch and RC11. The zfs and zpool also hung up. |
@smallma Can you post the contents of |
behlendorf, Thanks. I'll keep track :) |
…object_agent/async-backtrace-attributes-0.2.6 Bump async-backtrace-attributes from 0.2.5 to 0.2.6 in /cmd/zfs_object_agent
Hello all,
I got a problem of SPLError as below when there are a lots of I/O. Please help me out. Thank you.
The text was updated successfully, but these errors were encountered: