This allows arguments that take things like paths
(e.g. -l dir=/somewhere) to be handled properly.
Signed-off-by: Alexander Guy alexan...@andern.org
---
debian/sheepdog.postinst | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/sheepdog.postinst b/debian/sheepdog.postinst
index
At Mon, 2 Feb 2015 14:12:41 -0800,
Alexander Guy wrote:
This allows arguments that take things like paths
(e.g. -l dir=/somewhere) to be handled properly.
Signed-off-by: Alexander Guy alexan...@andern.org
---
debian/sheepdog.postinst | 1 +
1 file changed, 1 insertion(+)
Applied,
At Mon, 02 Feb 2015 18:23:03 +0900,
Hitoshi Mitake wrote:
At Mon, 2 Feb 2015 14:58:18 +0900,
Takafumi Fujieda wrote:
Current, deleted vids are not reused, without cutting relations.
If snapshots of many online vdis in a cluster are created continuously,
the vid space will be
From: Wang Dongxu wangdon...@cmss.chinamobile.com
Since commit 4fea6f95a2de90f45f90415f289083c6b29120a7, dog cluster info change
its output format, to make sure tests/functional cases are suitable for the new
format, modified these output.
Signed-off-by: Wang Dongxu
On Tue, Feb 03, 2015 at 12:19:12PM +0800, Wang Dongxu wrote:
Since commit 4fea6f95a2de90f45f90415f289083c6b29120a7, dog cluster info change
its output format, to make sure tests/functional cases are suitable for the
new
format, modified these output.
Signed-off-by: Wang Dongxu
On Mon, Jan 19, 2015 at 07:28:53PM +0900, Hitoshi Mitake wrote:
dog vdi snapshot vdi --no-share has a bottleneck: the dog
process. This patch adds a new option --fast-deep-copy to dog vdi
snapshot, which avoid the bottleneck.
It seems to me --no-share and --fast-deep-copy has some relations,
On Mon, Feb 02, 2015 at 06:18:52PM +0900, Hitoshi Mitake wrote:
Current sheep cannot handle a case like this:
1. iterate snapshot creation and let latest working VDI have VID 0xff
2. create one more snapshot
(The situation can be reproduced with the below sequence:
$ dog vdi create
Since commit 4fea6f95a2de90f45f90415f289083c6b29120a7, dog cluster info change
its output format, to make sure tests/functional cases are suitable for the new
format, modified these output.
Signed-off-by: Wang Dongxu wangdon...@cmss.chinamobile.com
---
tests/functional/001.out | 36
At Tue, 3 Feb 2015 11:55:34 +0800,
Liu Yuan wrote:
On Mon, Feb 02, 2015 at 06:18:52PM +0900, Hitoshi Mitake wrote:
Current sheep cannot handle a case like this:
1. iterate snapshot creation and let latest working VDI have VID 0xff
2. create one more snapshot
(The situation can be
Am 2015-02-03 04:47, schrieb Liu Yuan:
It seems to me --no-share and --fast-deep-copy has some relations, they
all try
to achieve the same purpose, right? But the wording quit differs, which
might
cause troulbe for uesrs to understand.
How about --no-share and --no-share-fast?
Cheers
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
Sorry, this patch didn't work well.
Please ignore this patch.
But there is problem on vid wrap around.
From: fukumoto.yoshif...@lab.ntt.co.jp
To: sheepdog@lists.wpkg.org
Cc: FUKUMOTO Yoshifumi fukumoto.yoshif...@lab.ntt.co.jp
Subject: [sheepdog] [PATCH] sheep: fix vid wrap around
Message-ID:
Current sheep cannot handle a case like this:
1. iterate snapshot creation and let latest working VDI have VID 0xff
2. create one more snapshot
(The situation can be reproduced with the below sequence:
$ dog vdi create 00471718 1G
$ dog vdi snapshot 00471718 (repeat 7 times) )
In this
At Mon, 2 Feb 2015 14:58:18 +0900,
Takafumi Fujieda wrote:
Current, deleted vids are not reused, without cutting relations.
If snapshots of many online vdis in a cluster are created continuously,
the vid space will be exhausted.
To be honest, it is hard for me to understand the motivation
14 matches
Mail list logo
