[sheepdog] [PATCH v2 0/3] sheep: writeback cache semantics in backend store

Hitoshi Mitake mitake.hitoshi at lab.ntt.co.jp
Tue Sep 4 08:41:45 CEST 2012


(2012/09/03 16:15), Liu Yuan wrote:
> On 09/03/2012 03:08 PM, Hitoshi Mitake wrote:
>>
>> BTW, I have two questions.
>>
>> How many iteration did it take to produce this segfault?
>> It seems that reproducing this segfault is hard, it happens rarely on my
>> environment.
>>
>
> Less than 10 times, but it depends, what I am sure is I can get the seg
> fault when some time elapse.

On my environment, I needed to iterate more than few ten times to 
reproduce the bug.
In addition, the crash of sheep on my environment might not be segfault.
Instead of core dump, I could find this output in 026.out.bad:

QA output created by 026
using backend farm store
[main] do_read(275) failed to read from socket: -1
[main] exec_req(362) failed to read a response
failed to connect to  127.0.0.1:7005
42

Have you ever seen this output?
It seems that sheep is interrupted by the signal. I'm trying to obtain 
more information about this error.

Thanks,
Hitoshi





More information about the sheepdog mailing list