[sheepdog-users] Issue: get_vnode_info must be called in main thread
Ruoyu
liangry at ucweb.com
Tue Jul 29 05:41:35 CEST 2014
On 2014年07月29日 10:38, 王力锋 wrote:
> Thank you very much for your information..
> I have reported the issue to the tracker.
> https://bugs.launchpad.net/sheepdog-project/+bug/1349659
> Please feel free to connect with me if you want more detailed information.
>
> Now is there a work around for this issue?
Trace only reports an error and the bug might caused by md module.
Could you please check your sheep's version? Just execute sheep -v in
command line.
>
> 在 2014-07-29 10:04:55,"Ruoyu" <liangry at ucweb.com> 写道:
>
>
> On 2014年07月28日 19:40, 王力锋 wrote:
>> No. I just enable the features as follows.
>> ./configure --enable-zookeeper --enable-sheepfs --enable-http
>> --enable-debug
> That is it. --enable-debug will trigger --enable-trace. It seems
> it is a critical bug in trace module.
>>
>> I doubt that the http service feature may be the root cause of
>> this issue.
>> At 2014-07-28 06:23:01, "Ruoyu"<liangry at ucweb.com> wrote:
>> >Are you using trace module, in another word, --enable-trace when ./configure?
>> >
>> >-----
>> >
>> > wrote
>> >
>> >
>> > I create a sheepdog cluster and enable the Erasure Code feature. My cluster has 10 nodes and the erasure code is 8:2.
>> > However after one node of my cluster down, all the sheepdog service in other nodes are all down.
>> > In my opinion, the cluster should tolerate 2 nodes' failure. Do you meet the same issue?
>> > I enable the http service and use the zookeeper driver.
>> >
>> >The logs are as follows:
>> >Jul 28 11:03:43 DEBUG [main] zk_watcher(704) path:/sheepdog/member/IPv4 ip:192.168.10.11 port:7000, type:2, state:3
>> >Jul 28 11:03:43 DEBUG [main] update_epoch_log(26) update epoch: 2, 9
>> >Jul 28 11:03:43 DEBUG [main] for_each_object_in_path(200) /mnt/disk11, 00da5c25d0a3bbc8_0
>> >Jul 28 11:03:43 DEBUG [main] for_each_object_in_path(200) /mnt/disk10, 00da5c254560f353_6
>> >Jul 28 11:03:43 EMERG [main] thread_check_enter(62) PANIC: get_vnode_info must be called in main thread
>> >Jul 28 11:03:43 EMERG [main] thread_check_enter(62) PANIC: get_vnode_info must be called in main thread
>> >Jul 28 11:03:43 EMERG [main] crash_handler(267) sheep exits unexpectedly (Aborted).
>> >
>> >
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog-users/attachments/20140729/eb2d8022/attachment-0005.html>
More information about the sheepdog-users
mailing list