2015-02-11 15:43 GMT+03:00 Liu Yuan namei.u...@gmail.com:
This scheme can build on the sheepdog's current features:
0 use qemu-img (recommenced because better performance) or dog to read the
base
vdi.
1 use dog to backup the delta data for different snapshots takben by
qemu-img
See http://jenkins.sheepdog-project.org:8080/job/sheepdog-build/631/changes
Changes:
[liuyuan] dog: type cast miss at vdi_show_progress
--
[...truncated 57 lines...]
checking for grep that handles long lines and -e... /bin/grep
checking for egrep...
On Tue, Feb 10, 2015 at 05:53:44PM +0900, Teruaki Ishizaki wrote:
A resizable max VDI size was fixed value, 4TB.
So, when block_size_shift was specified more than 22,
resizing VDI size over 4TB caused error.
This patch enables to calculate a resizable max VDI properly.
Signed-off-by:
On Wed, Feb 11, 2015 at 05:57:25PM +0400, Vasiliy Tolstov wrote:
2015-02-11 15:43 GMT+03:00 Liu Yuan namei.u...@gmail.com:
This scheme can build on the sheepdog's current features:
0 use qemu-img (recommenced because better performance) or dog to read the
base
vdi.
1 use dog to
On Thu, Feb 12, 2015 at 10:51:25AM +0900, Teruaki Ishizaki wrote:
(2015/02/10 20:12), 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
On Thu, Feb 12, 2015 at 11:33:16AM +0900, Teruaki Ishizaki wrote:
(2015/02/12 11:19), Liu Yuan wrote:
On Thu, Feb 12, 2015 at 10:51:25AM +0900, Teruaki Ishizaki wrote:
(2015/02/10 20:12), Liu Yuan wrote:
On Tue, Jan 27, 2015 at 05:35:27PM +0900, Teruaki Ishizaki wrote:
Previously, qemu block
Hi all,
who has the right permission to install yasm on the sheepdog Jenkins server?
Our list is annoyed everyday, please save us from it.
Thanks
Yuan
--
sheepdog mailing list
sheepdog@lists.wpkg.org
https://lists.wpkg.org/mailman/listinfo/sheepdog
(2015/02/10 20:12), 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
(2015/02/12 11:19), Liu Yuan wrote:
On Thu, Feb 12, 2015 at 10:51:25AM +0900, Teruaki Ishizaki wrote:
(2015/02/10 20:12), 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
On Thu, Feb 12, 2015 at 04:40:56PM +0900, Hitoshi Mitake wrote:
At Thu, 12 Feb 2015 15:31:15 +0800,
Liu Yuan wrote:
On Thu, Feb 12, 2015 at 03:59:51PM +0900, Hitoshi Mitake wrote:
At Thu, 12 Feb 2015 14:38:37 +0800,
Liu Yuan wrote:
On Mon, Feb 09, 2015 at 05:25:48PM +0900,
Since code is printf(%s\n, sd_strerror(rsp-result));, 052.out should add
a new line.
Signed-off-by: Wang dongxu wangdon...@cmss.chinamobile.com
---
tests/functional/052.out | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/functional/052.out b/tests/functional/052.out
index
QEMU and sheepdog changes some output formats while upgrading to new version, so
tests/functional test cases need some changes.
Wang dongxu (5):
tests: avoid qemu-io warning
tests: avoid qemu-img snapshot warning
tests: correct vdi list
tests: fix content of 052.out
tests:fix vnode
qemu-io command add a warning message because probing a raw img is dangerous. So
add -f option to avoid this.
Signed-off-by: Wang dongxu wangdon...@cmss.chinamobile.com
---
tests/functional/013 | 6 +++---
tests/functional/017 | 2 +-
tests/functional/024 | 6 +++---
tests/functional/025 | 4
At Thu, 12 Feb 2015 15:00:49 +0800,
Liu Yuan wrote:
On Thu, Feb 12, 2015 at 03:19:21PM +0900, Hitoshi Mitake wrote:
At Tue, 10 Feb 2015 18:35:58 +0800,
Liu Yuan wrote:
On Tue, Feb 10, 2015 at 06:56:33PM +0900, Teruaki Ishizaki wrote:
(2015/02/10 17:58), Liu Yuan wrote:
On
On Mon, Feb 09, 2015 at 05:25:48PM +0900, Hitoshi Mitake wrote:
Current dog vdi snapshot command creates a new snapshot
unconditionally, even if a working VDI doesn't have its own
objects. In such a case, the created snapshot is redundant because
same VDI is already existing.
What kind of use
On Thu, Feb 12, 2015 at 04:28:01PM +0900, Hitoshi Mitake wrote:
At Thu, 12 Feb 2015 15:00:49 +0800,
Liu Yuan wrote:
On Thu, Feb 12, 2015 at 03:19:21PM +0900, Hitoshi Mitake wrote:
At Tue, 10 Feb 2015 18:35:58 +0800,
Liu Yuan wrote:
On Tue, Feb 10, 2015 at 06:56:33PM +0900,
At Thu, 12 Feb 2015 15:31:15 +0800,
Liu Yuan wrote:
On Thu, Feb 12, 2015 at 03:59:51PM +0900, Hitoshi Mitake wrote:
At Thu, 12 Feb 2015 14:38:37 +0800,
Liu Yuan wrote:
On Mon, Feb 09, 2015 at 05:25:48PM +0900, Hitoshi Mitake wrote:
Current dog vdi snapshot command creates a new
In the current sheepdog, when sheepdog crashed,
there is too little information about the signal source.
This patch use (*handler)(int, siginfo_t *, void *)
instead of (*handler)(int). In this way, can show more detail of the
crash problem, especially the pid of singal sender
Cc: Hitoshi Mitake
qemu-img snapshot option will print warining message while probing a raw
image, so
filter them using sed.
Signed-off-by: Wang dongxu wangdon...@cmss.chinamobile.com
---
tests/functional/013 | 2 +-
tests/functional/017 | 12 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
diff
dog vdi list add column Block Size Shift, add them to test cases.
Signed-off-by: Wang dongxu wangdon...@cmss.chinamobile.com
---
tests/functional/073.out | 2 +-
tests/functional/081.out | 6 +++---
tests/functional/082.out | 6 +++---
tests/functional/087.out | 10 +-
At Wed, 11 Feb 2015 23:44:53 -0800,
Wang Zhengyong wrote:
In the current sheepdog, when sheepdog crashed,
there is too little information about the signal source.
This patch use (*handler)(int, siginfo_t *, void *)
instead of (*handler)(int). In this way, can show more detail of the
crash
In the current sheepdog, when sheepdog crashed,
there is too little information about the signal source.
This patch use (*handler)(int, siginfo_t *, void *)
instead of (*handler)(int). In this way, can show more detail of the
crash problem, especially the pid of singal sender
Cc: Hitoshi Mitake
since commit 5fed9d6, Cluster vnodes strategy information is produced,
so fix them in test cases.
Signed-off-by: Wang dongxu wangdon...@cmss.chinamobile.com
---
tests/functional/030.out | 1 +
tests/functional/096.out | 2 ++
2 files changed, 3 insertions(+)
diff --git
On Thu, Feb 12, 2015 at 03:19:21PM +0900, Hitoshi Mitake wrote:
At Tue, 10 Feb 2015 18:35:58 +0800,
Liu Yuan wrote:
On Tue, Feb 10, 2015 at 06:56:33PM +0900, Teruaki Ishizaki wrote:
(2015/02/10 17:58), Liu Yuan wrote:
On Tue, Feb 10, 2015 at 05:22:02PM +0900, Teruaki Ishizaki wrote:
At Thu, 12 Feb 2015 14:38:37 +0800,
Liu Yuan wrote:
On Mon, Feb 09, 2015 at 05:25:48PM +0900, Hitoshi Mitake wrote:
Current dog vdi snapshot command creates a new snapshot
unconditionally, even if a working VDI doesn't have its own
objects. In such a case, the created snapshot is
On Thu, Feb 12, 2015 at 03:59:51PM +0900, Hitoshi Mitake wrote:
At Thu, 12 Feb 2015 14:38:37 +0800,
Liu Yuan wrote:
On Mon, Feb 09, 2015 at 05:25:48PM +0900, Hitoshi Mitake wrote:
Current dog vdi snapshot command creates a new snapshot
unconditionally, even if a working VDI doesn't
At Wed, 11 Feb 2015 21:47:41 -0800,
Wang Zhengyong wrote:
In the current sheepdog, when sheepdog crashed,
there is too little information about the signal source.
This patch use (*handler)(int, siginfo_t *, void *)
instead of (*handler)(int). In this way, can show more detail of the
crash
From: Liu Yuan liuy...@cmss.chinamobile.com
Signed-off-by: Liu Yuan liuy...@cmss.chinamobile.com
---
sheep/cluster/zookeeper.c | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/sheep/cluster/zookeeper.c b/sheep/cluster/zookeeper.c
index
On Sun, Feb 08, 2015 at 08:46:01PM +0100, Corin Langosch wrote:
Hi guys,
afaik sheepdog uses consistent hashing to map objects to nodes. But how do
you choose where the individual ec-chunks of
an object should go? Consistent hashing cannot be used here because different
ec-chunks of the
On Wed, Feb 11, 2015 at 03:57:32PM +0400, Vasiliy Tolstov wrote:
Hi! I need to store user backups and allows to download it. I see in
google that sheepdog supports deduplication, but can't find info in
sheepdog docs about it. Does sheepdog support deduplication?
This deduplication is for SD's
Hi! I need to store user backups and allows to download it. I see in
google that sheepdog supports deduplication, but can't find info in
sheepdog docs about it. Does sheepdog support deduplication?
Also i think not use cluster wide snapshots because i want to dedicate
backup server from other
2015-02-11 15:08 GMT+03:00 Liu Yuan namei.u...@gmail.com:
On Wed, Feb 11, 2015 at 03:57:32PM +0400, Vasiliy Tolstov wrote:
Hi! I need to store user backups and allows to download it. I see in
google that sheepdog supports deduplication, but can't find info in
sheepdog docs about it. Does
2015-02-11 15:28 GMT+03:00 Liu Yuan namei.u...@gmail.com:
We need to what is user's backups. Is it the whole vdi or dalta data for
different vdis?
Best scheme as i think is:
1) If backup not exists for vdi - create full backup (this is simple
copy all data)
2) If backup already created -
On Wed, Feb 11, 2015 at 04:32:34PM +0400, Vasiliy Tolstov wrote:
2015-02-11 15:28 GMT+03:00 Liu Yuan namei.u...@gmail.com:
We need to what is user's backups. Is it the whole vdi or dalta data for
different vdis?
Best scheme as i think is:
1) If backup not exists for vdi - create full
On Wed, Feb 11, 2015 at 04:14:35PM +0400, Vasiliy Tolstov wrote:
2015-02-11 15:08 GMT+03:00 Liu Yuan namei.u...@gmail.com:
On Wed, Feb 11, 2015 at 03:57:32PM +0400, Vasiliy Tolstov wrote:
Hi! I need to store user backups and allows to download it. I see in
google that sheepdog supports
At Tue, 10 Feb 2015 18:35:58 +0800,
Liu Yuan wrote:
On Tue, Feb 10, 2015 at 06:56:33PM +0900, Teruaki Ishizaki wrote:
(2015/02/10 17:58), Liu Yuan wrote:
On Tue, Feb 10, 2015 at 05:22:02PM +0900, Teruaki Ishizaki wrote:
(2015/02/10 12:10), Liu Yuan wrote:
On Tue, Jan 27, 2015 at
36 matches
Mail list logo
