Previously dog vdi_alter_copy command was failed, because of using
a invalid block_size_shift.
This patch fix to use a right block_size_shift.
Signed-off-by: Teruaki Ishizaki ishizaki.teru...@lab.ntt.co.jp
---
dog/vdi.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
The result of the multiplication of uint32 and uint64 are rounded to uint32
So, Progress of the command is displayed back to 0%,
when it exceeds the boundaries of 32bit.
This is only a display issue, command processing can be completed.
Signed-off-by: Masaki Saeki saeki.mas...@po.ntts.co.jp
---
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 don't need to specify additional
At Tue, 10 Feb 2015 10:59:18 +0900,
Teruaki Ishizaki wrote:
Previously dog vdi_alter_copy command was failed, because of using
a invalid block_size_shift.
This patch fix to use a right block_size_shift.
Signed-off-by: Teruaki Ishizaki ishizaki.teru...@lab.ntt.co.jp
---
dog/vdi.c |1
On Tue, Feb 10, 2015 at 11:10:51AM +0800, 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.
From: Liu Yuan liuy...@cmss.chinamobile.com
Even with a 3 node cluster and only 1 vdi, killing one node and joining it back
the error message that buffer too small will pop out twice, this means 512 is
too small even for a single VDI cluster.
Making it as 4K will mitigat the problem a bit.
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.
This patch adds a new option -R to the dog command for reducing
the identical
This patch add a new test for the functionality of reducing identical
snapshots. With -R option, new snapshot isn't created if a VDI doesn't
have its own objects.
Signed-off-by: Hitoshi Mitake mitake.hito...@lab.ntt.co.jp
---
tests/functional/100 | 32
At Mon, 9 Feb 2015 16:21:43 +0800,
Liu Yuan wrote:
From: Liu Yuan liuy...@cmss.chinamobile.com
Even with a 3 node cluster and only 1 vdi, killing one node and joining it
back
the error message that buffer too small will pop out twice, this means 512
is
too small even for a single VDI
On Tue, Feb 10, 2015 at 03:03:56PM +0900, Saeki Masaki wrote:
The result of the multiplication of uint32 and uint64 are rounded to uint32
So, Progress of the command is displayed back to 0%,
when it exceeds the boundaries of 32bit.
This is only a display issue, command processing can be
Even with a 3 node cluster and only 1 vdi, killing one node and joining it back
the error message that buffer too small will pop out twice, this means 512 is
too small even for a single VDI cluster.
Making it as 4K will mitigat the problem a bit.
Signed-off-by: Liu Yuan
At Sun, 08 Feb 2015 21:15:19 +0100,
Corin Langosch wrote:
Hi guys,
I'm currently digging around in the sheepdog sources and have a few questions
regarding recovery and object consistency.
Please correct me if I'm wrong in anything I write here - it's all just read
together from various
The existing Debian sysvinit scripts are using different
environment variable names for configuration than those
present in the upstream systemd service file (e.g. DAEMON_ARGS).
This naming difference breaks sheepdog on Debian installs that
are using sysvinit and then migrate to systemd.
This
See http://jenkins.sheepdog-project.org:8080/job/sheepdog-build/629/changes
Changes:
[mitake.hitoshi] sheep: increase buffer while in cinfo collection
--
[...truncated 57 lines...]
checking for grep that handles long lines and -e... /bin/grep
checking for
14 matches
Mail list logo
