I am using sheepdog 0.2.4 since its out without any Problems, yesterday
I start upgrading to current git version, but one of my virtual machines crashed the hole cluster... Other Machines seems to work without Problems..

Steps for repoducing it in a very stripped down environment.
Using the image sv-bss-visu.qcow2 in the old 0.2.4 environment
works without problems...

root@sv-it-cloud3:~# sheep /mnt/soeren-1/

root@sv-it-cloud2:~# sheep /mnt/soeren-1/
root@sv-it-cloud2:~# collie cluster format --copies=2
root@sv-it-cloud2:~# qemu-img convert sv-bss-visu.qcow2 sheepdog:sv-bss-visu

Then starting the virtual Machine and wait for the crash...
(I manage all of my virtual machines with libvirt)

The complete logfiles for the test are attached.

If more infos are needed, please give me a short note.

Cheers

Bastian


Jun 08 09:19:36 send_join_request(891) IPv4 ip:10.0.1.62 port:7000
Jun 08 09:19:36 main(302) sheepdog daemon (version 0.3.0_386_g0ae0add) started
Jun 08 09:19:36 update_cluster_info(697) status = 2, epoch = 0, 0, 0
Jun 08 09:19:38 update_cluster_info(697) status = 2, epoch = 0, 0, 1
Jun 08 09:19:43 queue_cluster_request(350) 0x1e45290 84
Jun 08 09:19:43 trunk_reset(400) clean
Jun 08 09:19:43 init_sys_vdi_bitmap(290) found the working directory 
/mnt/soeren-1//obj/
Jun 08 09:19:49 queue_cluster_request(350) 0x1e45290 11
Jun 08 09:19:49 do_lookup_vdi(226) looking for sv-bss-visu (dc4435)
Jun 08 09:19:49 add_vdi(321) creating new vdi sv-bss-visu: size 42948325376, 
vid dc4435, base 0, cur 0
Jun 08 09:19:49 add_vdi(326) using default replication level of 2 copies
Jun 08 09:19:49 post_cluster_new_vdi(131) done 0 14435381
Jun 08 09:19:49 queue_cluster_request(350) 0x1e45390 12
Jun 08 09:19:49 do_lookup_vdi(226) looking for sv-bss-visu (dc4435)
Jun 08 09:22:58 queue_cluster_request(350) 0x21a6290 13
Jun 08 09:24:44 io_op_done(119) leaving sheepdog cluster
Jun 08 09:24:44 do_read(255) failed to read from socket: Success
Jun 08 09:24:44 exec_req(352) failed to read the response data: Success
Jun 08 09:24:44 fetch_object_list(493) failed, 1, 25
Jun 08 09:24:44 crash_handler(391) sheep pid 29027 exited unexpectedly.
Jun 08 09:19:56 send_join_request(891) IPv4 ip:10.0.1.63 port:7000
Jun 08 09:19:56 main(302) sheepdog daemon (version 0.3.0_386_g0ae0add) started
Jun 08 09:19:56 update_cluster_info(697) status = 2, epoch = 0, 0, 0
Jun 08 09:20:02 trunk_reset(400) clean
Jun 08 09:20:02 init_sys_vdi_bitmap(290) found the working directory 
/mnt/soeren-1//obj/
Jun 08 09:20:07 post_cluster_new_vdi(131) done 0 14435381
Jun 08 09:23:24 queue_cluster_request(350) 0x25ae7e0 12
Jun 08 09:23:24 do_lookup_vdi(226) looking for sv-bss-visu (dc4435)
Jun 08 09:25:03 forward_write_obj_req(193) fail 25
Jun 08 09:25:03 fix_object_consistency(265) failed to write object 19
Jun 08 09:25:03 fetch_object_list(493) failed, 0, 25
Jun 08 09:25:03 forward_write_obj_req(193) fail 25
Jun 08 09:25:03 fix_object_consistency(265) failed to write object 19
Jun 08 09:25:03 forward_write_obj_req(149) fail to write local 65
Jun 08 09:25:03 fix_object_consistency(265) failed to write object 41
Jun 08 09:25:03 forward_write_obj_req(149) fail to write local 65
Jun 08 09:25:03 fix_object_consistency(265) failed to write object 41
Jun 08 09:25:03 crash_handler(391) sheep pid 14462 exited unexpectedly.
-- 
sheepdog mailing list
sheepdog@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/sheepdog

Reply via email to