On 04/08/2015 06:20 PM, Justin Clift wrote:
Hi Pranith,
Hagarth mentioned in the weekly IRC meeting that you have an
idea what might be causing the regression tests to generate
cores?
Can you outline that quickly, as Jeff has some time and might
be able to help narrow it down further. :)
(and these core files are really annoying :/)
I feel it is a lot like
https://bugzilla.redhat.com/show_bug.cgi?id=1184417. clear-locks command
is not handled properly after we did the client_t refactor. I believe
that is the reason for the crashes but I could be wrong. But After
looking at the code I feel there is high probability that this is the
issue. I didn't find it easy to fix. We will need to change the lock
structure list maintenance heavily. Easier thing would be to disable
clear-locks functionality tests in the regression as it is not something
that is used by the users IMO and see if it indeed is the same issue.
There are 2 tests using this command:
18:34:00 :) ⚡ git grep clear-locks tests
tests/bugs/disperse/bug-1179050.t:TEST $CLI volume clear-locks $V0 /
kind all inode
tests/bugs/glusterd/bug-824753-file-locker.c: "gluster volume
clear-locks %s /%s kind all posix 0,7-1 |"
If even after disabling these two tests it fails then we will need to
look again. I think jeff's patch which will find the test which
triggered the core should help here.
Pranith
Regards and best wishes,
Justin Clift
--
GlusterFS - http://www.gluster.org
An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.
My personal twitter: twitter.com/realjustinclift
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
