Re: [sheepdog] [PATCH v4] sheepdog: selectable object size support

2015-02-03 Thread Teruaki Ishizaki
(2015/02/02 15:52), Liu Yuan wrote: On Tue, Jan 27, 2015 at 05:35:27PM +0900, Teruaki Ishizaki wrote: Previously, qemu block driver of sheepdog used hard-coded VDI object size. This patch enables users to handle block_size_shift value for calculating VDI object size. When you start qemu, you

[sheepdog] [PATCH 2/3] sheep: error messages in recovery is too frequently

2015-02-03 Thread Saeki Masaki
lacking objects during recovery is acceptable in the range of redundancy. So it is not necessary to show all error messages This problem occurs only in EC. because, ec object have not replicated object. Signed-off-by: Masaki Saekisaeki.mas...@po.ntts.co.jp --- sheep/recovery.c |2 +- 1

[sheepdog] [PATCH 1/3] sheep: error messages during buffer resize

2015-02-03 Thread Saeki Masaki
execute opcode VDI_STATE_SNAPSHOT_CTL, sheepdog resize buffer if needed, so this situation is not error. Signed-off-by: Masaki Saekisaeki.mas...@po.ntts.co.jp --- sheep/ops.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/sheep/ops.c b/sheep/ops.c index

[sheepdog] [PATCH 0/3] sheep: adjust error loglevel

2015-02-03 Thread Saeki Masaki
Some Sheepdog ERROR message information can not be said to be an error. These log, confuse the user unfamiliar to Sheepdog. So, we would like to suggest to reduce the level of some log. Signed-off-by: Masaki Saekisaeki.mas...@po.ntts.co.jp --- sheep/ops.c |2 +- sheep/recovery.c |

[sheepdog] [PATCH 3/3] sheep: error massages in sheep_exec_request

2015-02-03 Thread Saeki Masaki
normally sheep_exec_request succeeded by retry request. However, always sheep_exec_request shows ERROR. level of logs WARN is desirable. Signed-off-by: Masaki Saekisaeki.mas...@po.ntts.co.jp --- sheep/request.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

Re: [sheepdog] Redundancy policy via iSCSI

2015-02-03 Thread Hitoshi Mitake
At Tue, 03 Feb 2015 17:02:24 +0900, Hitoshi Mitake wrote: Hi Hu, Thanks for your report! At Tue, 3 Feb 2015 15:52:12 +0800, hujianyang wrote: Hi Hitoshi, Sorry for disturb. I'm testing redundancy policy of sheepdog via iSCSI. I think if I create a 1G v-disk, the total

Re: [sheepdog] Redundancy policy via iSCSI

2015-02-03 Thread Hitoshi Mitake
Hi Hu, Thanks for your report! At Tue, 3 Feb 2015 15:52:12 +0800, hujianyang wrote: Hi Hitoshi, Sorry for disturb. I'm testing redundancy policy of sheepdog via iSCSI. I think if I create a 1G v-disk, the total space cost of this device should be 3*1G under a 3 copies policy. But

Re: [sheepdog] Redundancy policy via iSCSI

2015-02-03 Thread hujianyang
Hi Hitoshi, Thanks for your help! Try to answer your questions. On 2015/2/3 16:02, Hitoshi Mitake wrote: Hmm, seems strange. For diagnosing, I have some questions: 1. Can you see any error messages in log files of sheep? log while performing dd on a formatted filesystem: Feb 04 00:16:05

[sheepdog] Build failed in Jenkins: sheepdog-build #623

2015-02-03 Thread sheepdog-jenkins
See http://jenkins.sheepdog-project.org:8080/job/sheepdog-build/623/changes Changes: [mitake.hitoshi] deb: escape forward slashes in DAEMON_ARGS [liuyuan] Change tests outputs to be suitable for new cluster info format -- [...truncated 57 lines...]

Re: [sheepdog] Redundancy policy via iSCSI

2015-02-03 Thread hujianyang
On 2015/2/3 17:19, Bastian Scholz wrote: Am 2015-02-03 09:54, schrieb hujianyang: I'm not clear with this. Just run sheep /mnt/store/0 -z 0 -p 7000 on each host. I guess this is your problem. Sheep replicates in different zones, since you have only one zone defined, sheep dont replicate the

Re: [sheepdog] Redundancy policy via iSCSI

2015-02-03 Thread hujianyang
Hi Saeki, On 2015/2/3 16:53, Saeki Masaki wrote: Hi Hu, Since Sheepdog has a mechanism that does not place objects in the same zone_id. Can you try to change ZONE id in each node. Id Host:Port V-Nodes Zone 0 130.1.0.147:7000128 0 1