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
changelog: A brick process is getting crash due to SIGSEGV in changelog #3521
Comments
mohit84
added a commit
to mohit84/glusterfs
that referenced
this issue
May 13, 2022
A brick process is getting crashed while using glusterfind tool. The glusterfind tool uses changelog xlator and the xlator has race condition to handle crpc object list so at the time of calling ev_connector thread it is getting crashed. Solution: The xlator is not using correct lock to sync the list in crpc object so use crpc->lock to handle the crpc->list. Fixes: gluster#3521 Change-Id: I13ec8603dc06ecba4cd293cb48012a2ebef55749 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
mohit84
added a commit
to mohit84/glusterfs
that referenced
this issue
May 23, 2022
A brick process is getting crashed while using glusterfind tool. The glusterfind tool uses changelog xlator and the xlator has race condition to handle crpc object list so at the time of calling ev_connector thread it is getting crashed. Solution: The xlator is not using correct lock to sync the list in crpc object so use crpc->lock to handle the crpc->list. Fixes: gluster#3521 Change-Id: I13ec8603dc06ecba4cd293cb48012a2ebef55749 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
mohit84
added a commit
to mohit84/glusterfs
that referenced
this issue
May 23, 2022
A brick process is getting crashed while using glusterfind tool. The glusterfind tool uses changelog xlator and the xlator has race condition to handle crpc object list so at the time of calling ev_connector thread it is getting crashed. Solution: The xlator is not using correct lock to sync the list in crpc object so use crpc->lock to handle the crpc->list. Fixes: gluster#3521 Change-Id: I13ec8603dc06ecba4cd293cb48012a2ebef55749 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
xhernandez
pushed a commit
that referenced
this issue
Jun 27, 2022
A brick process is getting crashed while using glusterfind tool. The glusterfind tool uses changelog xlator and the xlator has race condition to handle crpc object list so at the time of calling ev_connector thread it is getting crashed. Solution: The xlator is not using correct lock to sync the list in crpc object so use crpc->lock to handle the crpc->list. Fixes: #3521 Change-Id: I13ec8603dc06ecba4cd293cb48012a2ebef55749 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A brick process is getting crashed while using glusterfind tool. The glusterfind tool uses changelog xlator and
the xlator has race condition to handle crpc object list so at the time of calling ev_connector thread it is getting
crashed.
Below is the volume configuration
Below is the stack dump from the glusterfsd core
The text was updated successfully, but these errors were encountered: