On 2014?09?04? 18:07, Valerio Pachera wrote:
2014-09-04 11:18 GMT+02:00 Valerio Pachera <siri...@gmail.com
<mailto:siri...@gmail.com>>:
It's fixed
The issue still show up in case of restoring a single vdi
Was the "restored" vdi saved by the old program and restored by the new
program?
If yes, the error message would be still existed because the in_use flag
of the deleted vdi was ignored while saving, but it could not be ignored
while restoring.
Further more, the message won't do anything harmful to your system.
root@test006:/media/pubblica/tmp# time dog cluster snapshot load terzo
cluster_snapshots test
__
()'`;
/\|`
/ | Caution! The cluster is not empty.
(/_)_|_ Are you sure you want to continue? [yes/no]: yes
using backend plain store
100.0 %
[=====================================================================================================================================================]
1324 / 1324
real 2m38.087s
user 0m40.108s
sys 0m24.688s
root@test006:/media/pubblica/tmp# dog vdi list
Name Id Size Used Shared Creation time VDI id
Copies Tag
Failed to read object 807c2b2500000000 No object found
Failed to read inode header
s test 2 5.0 GB 0.0 MB 5.0 GB 2014-09-04 10:50 7c2b26 2
s test 3 5.0 GB 164 MB 4.8 GB 2014-09-04 11:12 7c2b27 2
s test 4 5.0 GB 0.0 MB 5.0 GB 2014-09-04 11:23 7c2b28 2
test 0 5.0 GB 0.0 MB 5.0 GB 2014-09-04 11:57 7c2b29 2
--
sheepdog mailing list
sheepdog@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/sheepdog
