[sheepdog] [RFC PATCH] object cache: revert object_cache_pull() to older version

Yibin Shen zituan at taobao.com
Wed Jun 6 10:04:52 CEST 2012


hmm, I can reproduce this issue by followed steps:

1) insert a base image to sheep cluster.
2) clone 2 ~ 3 vm per each host.
3) start all vm simultaneously.

then I can see the random return value

On Tue, Jun 5, 2012 at 6:22 PM, MORITA Kazutaka
<morita.kazutaka at lab.ntt.co.jp> wrote:
> At Tue, 05 Jun 2012 16:43:05 +0800,
> Liu Yuan wrote:
>>
>> On 06/04/2012 04:53 PM, MORITA Kazutaka wrote:
>>
>> > One possibility is that if forward_write_obj_req() fails before
>> > receiving data, the next forward_(read|write)_obj_req() could be
>> > interleaved.
>> >
>> > The below untested patch may fix the problem though the approach is a
>> > poor way.
>>
>>
>> This fix doesn't fix anything.
>
> I think my patch will fix the bug I said above, though it doesn't fix
> your problem.
>
>> I wrote a workaround: use connect_to()
>> inside forward_write_obj_req(), and close(fd) when out of function. The
>> problem is gone.
>
> I have no idea why the problem happens for now.  I've not reproduced
> it yet on my environment.
>
> Thanks,
>
> Kazutaka
> --
> sheepdog mailing list
> sheepdog at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/sheepdog

________________________________

This email (including any attachments) is confidential and may be legally privileged. If you received this email in error, please delete it immediately and do not copy it or use it for any purpose or disclose its contents to any other person. Thank you.

本电邮(包括任何附件)可能含有机密资料并受法律保护。如您不是正确的收件人,请您立即删除本邮件。请不要将本电邮进行复制并用作任何其他用途、或透露本邮件之内容。谢谢。



More information about the sheepdog mailing list