> Collie vdi track without the -i option just tracks where the vdi > metadata object is located. Given that you formatted with --nr-copies=1 > there is just one copy. > > Try adding -i 0, -i 1, etc. > ok, so index is like a 4M block? 400M vdi -> index 0 - 99 root at sheep01:~# collie vdi object -i 99 test Looking for the object 0x7c2b2500000063 (the inode vid 0x7c2b25 idx 99) with 2 nodes 172.30.0.80:7000 doesn't have the object 172.30.0.80:7001 has the object (should be 1 copies) root at sheep01:~# collie vdi object -i 100 test Looking for the object 0x7f30d5abfe60 (the inode vid 0x7c2b25 idx 100) with 2 nodes 172.30.0.80:7000 doesn't have the object 172.30.0.80:7001 doesn't have the object max. index -> 1048575 root at sheep01:~# collie vdi object -i 1048575 test Looking for the object 0x554e47000fffff (the inode vid 0x7c2b25 idx 1048575) with 2 nodes 172.30.0.80:7000 doesn't have the object 172.30.0.80:7001 doesn't have the object root at sheep01:~# collie vdi object -i 1048576 test The offset is too large! means max. vdi size is 4095,99G -> ~ 4T |