(2014/12/03 21:18), Liu Yuan wrote:
On Wed, Dec 03, 2014 at 08:01:16PM +0900, Saeki Masaki wrote:
Hi, Yuan
Thank you for your comment.
but, SD_OP_READ_DEL_VDIS is already defined in "internal_proto.h" as below.
---
#include "sheepdog_proto.h"
---
So, I think need not be add again.
Really? a
On Wed, Dec 03, 2014 at 08:01:16PM +0900, Saeki Masaki wrote:
> Hi, Yuan
>
> Thank you for your comment.
> but, SD_OP_READ_DEL_VDIS is already defined in "internal_proto.h" as below.
> ---
> #include "sheepdog_proto.h"
> ---
>
> So, I think need not be add again.
>
Really? am I missing somethin
Hi, Yuan
Thank you for your comment.
but, SD_OP_READ_DEL_VDIS is already defined in "internal_proto.h" as below.
---
#include "sheepdog_proto.h"
---
So, I think need not be add again.
Regards,
Masaki Saeki.
(2014/12/03 18:14), Liu Yuan wrote:
On Wed, Nov 26, 2014 at 10:50:46AM +0900, Saeki Ma
On Wed, Nov 26, 2014 at 10:50:46AM +0900, Saeki Masaki wrote:
> For day-to-day backup, repeatedly create snapshot and delete snapshot.
> but inode file remains even after delete snapshot.
> "dog vdi list" command would read all inode files, even if vdi/snapshot was
> deleted.
> this behavior is in
At Wed, 26 Nov 2014 10:50:46 +0900,
Saeki Masaki wrote:
>
> For day-to-day backup, repeatedly create snapshot and delete snapshot.
> but inode file remains even after delete snapshot.
> "dog vdi list" command would read all inode files, even if vdi/snapshot was
> deleted.
> this behavior is ineff
For day-to-day backup, repeatedly create snapshot and delete snapshot.
but inode file remains even after delete snapshot.
"dog vdi list" command would read all inode files, even if vdi/snapshot was
deleted.
this behavior is inefficient to get current VDI list.
This patch manages the deleted VDI i
