On 2015/2/8 19:24, Vasiliy Tolstov wrote:
>
> 2015-02-07 5:03 GMT+03:00 hujianyang <mailto:hujiany...@huawei.com>>:
>
> KB/sreadrandreadwrite randwrite
> local 179957 36262 179933 66752
> iS
On 2015/2/6 16:41, Hitoshi Mitake wrote:
> At Wed, 04 Feb 2015 11:24:21 +0900,
> Hitoshi Mitake wrote:
>>
>> At Tue, 3 Feb 2015 17:17:42 +0800,
>> hujianyang wrote:
>>>
>>> Hi Saeki,
>>>
>>> On 2015/2/3 16:53, Saeki Masaki wrote:
>&g
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
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
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
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 after tests, I
find the cost of this device is only 1G. Seems no additional
copy is created.
I don'
l without
changing messages format and of course fix the messages
always printing problem.
Signed-off-by: hujianyang
---
sbd/sbd.h | 32 +++-
1 files changed, 3 insertions(+), 29 deletions(-)
diff --git a/sbd/sbd.h b/sbd/sbd.h
index c0b9ef3..5da4a90 100644
--- a/s
On 2015/1/20 11:01, Hitoshi Mitake wrote:
> At Tue, 20 Jan 2015 11:46:32 +0900,
> Hitoshi Mitake wrote:
>>
>> Cc: hujianyang
>> Signed-off-by: Hitoshi Mitake
>> ---
>> sbd/sheep_block_device.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
On 2015/1/20 10:49, Hitoshi Mitake wrote:
> At Tue, 20 Jan 2015 10:46:38 +0800,
> hujianyang wrote:
>>
>> On 2015/1/20 10:32, Hitoshi Mitake wrote:
>>>> I did a little change and it compiles OK. But UINT*_C are widely
>>>> used in sheepdog_proto.h so maybe
On 2015/1/20 10:32, Hitoshi Mitake wrote:
>> I did a little change and it compiles OK. But UINT*_C are widely
>> used in sheepdog_proto.h so maybe a large-scale modification is
>> needed?
>
> Cc-ing Alexander. The above UINT*_C macro problem is solved by the
> recent patch of Alexander. But the ks
On 2015/1/20 10:19, Hitoshi Mitake wrote:
> At Mon, 19 Jan 2015 12:39:44 -0800,
> Alexander Guy wrote:
>>
>> The Linux kernel headers don't have the *_C suffix macros, so
>> they can't be used in a header file shared between sheepdog userspace
>> and the sbd kernel module.
>>
>> Signed-off-by: Alex
Hi Hitoshi,
On 2015/1/16 17:40, Hitoshi Mitake wrote:
>>
>
> Hmm, could you show your yasm version? My yasm (1.2.0) can build
> current master branch with no problems.
>
> Thanks,
> Hitoshi
>
Thanks for your advise. I've updated my yasm to 1.3.0 and found it's
OK. I think maybe we should mark
On 2015/1/16 17:40, Hitoshi Mitake wrote:
>
> Hi Hu,
>
> At Fri, 16 Jan 2015 16:43:22 +0800,
> hujianyang wrote:
>>
>> Hi Hitoshi,
>>
>> I'm a learner of sheepdog. Here is two issues about setting
>> up sheepdog in my environment.
>>
>&g
Hi Hitoshi,
I'm a learner of sheepdog. Here is two issues about setting
up sheepdog in my environment.
1) invalid option '-d' in README
"""
To set up a 3 node cluster using local driver in one liner bash with debug mode:
$ mkdir /path/to/store
$ for i in 0 1 2; do sheep -c local -d
14 matches
Mail list logo
