[Gluster-devel] brick stop responding (3.4.0qa8)

[Emmanuel Dreyfus]

Anand Avati <anand.avati at gmail.com> wrote:

> Now you are showing a segfault backtrace from glusterd, while previously
> (the "single thread" backtrace) was from glusterfsd. Are both having
> problems?

As I said, it is unrelated: it appears just because I linked with
-lefence. That bug is usually hidden but since it is there I suggest it
could be fixed. I understand this is an off-by-one in an array
allocation?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org