[sheepdog-users] When does sheepdog flush the cache?

[Valerio Pachera]

2013/1/28 Valerio Pachera <sirio81 at gmail.com>:
> Instead of running 'collie vdi cache flush', I started a guest that
> uses the vdi.

I can tell you more: the guest reports I/O errors.
sheep.log reports lot's of  'failed to write object'

Jan 28 14:40:14 [main] send_join_request(1014) IPv4 ip:192.168.2.43 port:7000
Jan 28 14:40:14 [main] main(653) sheepdog daemon (version
0.5.5_62_gee9a5c6) started
Jan 28 14:40:14 [main] update_cluster_info(799) status = 2, epoch = 0,
finished: 0
Jan 28 14:40:35 [main] queue_cluster_request(315) MAKE_FS (0xef7a80)
Jan 28 14:41:12 [main] queue_cluster_request(315) NEW_VDI (0xefa020)
Jan 28 14:41:12 [block] do_lookup_vdi(393) looking for squeeze (a34c67)
Jan 28 14:41:12 [main] queue_cluster_request(315) NOTIFY_VDI_ADD (0xefa110)
Jan 28 14:41:12 [block] add_vdi(511) creating new vdi squeeze: size
10737418240, vid a34c67, base 0, cur 0, copies 2
Jan 28 14:41:12 [main] post_cluster_new_vdi(139) done 0 10701927
Jan 28 14:41:12 [main] queue_cluster_request(315) LOCK_VDI (0xef7ba0)
Jan 28 14:41:12 [block] do_lookup_vdi(393) looking for squeeze (a34c67)
Jan 28 14:41:38 [main] queue_cluster_request(315) RELEASE_VDI (0xf71990)
Jan 28 14:42:14 [main] queue_cluster_request(315) LOCK_VDI (0xef7a80)
Jan 28 14:42:14 [block] do_lookup_vdi(393) looking for squeeze (a34c67)
Jan 28 14:42:14 [main] queue_cluster_request(315) RELEASE_VDI (0xef7130)
Jan 28 14:42:14 [main] queue_cluster_request(315) LOCK_VDI (0xef7130)
Jan 28 14:42:14 [block] do_lookup_vdi(393) looking for squeeze (a34c67)
Jan 28 14:42:52 [gway 33102] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33102] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33101] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33104] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33104] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33103] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33106] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33106] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33105] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33108] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33108] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33107] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33110] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33110] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33109] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33112] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33112] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33111] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33114] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33114] wait_forward_request(205) fail 2
Jan 28 14:42:52 [gway 33113] write_cache_object(341) failed to write
object a34c6700000000, 2
Jan 28 14:42:52 [gway 33116] gateway_forward_request(308) fail to write local 2
Jan 28 14:42:52 [gway 33116] wait_forward_request(205) fail 2
----a lot more of these messages ---