[sheepdog-users] Issue: get_vnode_info must be called in main thread

[Hitoshi Mitake]

At Mon, 28 Jul 2014 11:23:44 +0800 (CST),
王力锋 wrote:
> 
> [1  <multipart/alternative (7bit)>]
> [1.1  <text/plain; GBK (base64)>]
> Hi, All
> 
> 
>         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).

Thanks for your report. It seems to be an important bug. This problem
was not caused by your usage, it was produced by internal error of
sheepdog.

Could you add an issue to our tracker?
https://bugs.launchpad.net/sheepdog-project/+filebug

Thanks,
Hitoshi


> [1.2  <text/html; GBK (base64)>]
> 
> [2  <text/plain; us-ascii (7bit)>]
> -- 
> sheepdog-users mailing lists
> sheepdog-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/sheepdog-users