[root at alcor var]# collie vdi list Name Id Size Used Shared Creation time VDI id id1538 1 100 GB 96 GB 0.0 MB 2011-11-28 15:36 2b2e41 id1503 1 50 GB 37 GB 0.0 MB 2011-11-25 18:26 2d5eff id1576 1 50 GB 24 GB 0.0 MB 2011-12-04 01:46 36a31b thz07 1 100 GB 98 GB 0.0 MB 2011-12-05 01:57 3d494c id1588 1 50 GB 45 GB 0.0 MB 2011-11-27 15:02 450f82 id1586 1 50 GB 19 GB 0.0 MB 2011-11-28 15:24 4512e8 id1584 1 50 GB 13 GB 0.0 MB 2011-12-04 01:57 45164e thzhost 1 25 GB 11 GB 0.0 MB 2011-11-09 16:02 56838b id1965 1 40 GB 0.0 MB 0.0 MB 2011-12-15 17:35 bc4747 id1946 1 50 GB 14 GB 0.0 MB 2011-12-06 15:51 c267a8 id1926 1 80 GB 43 GB 0.0 MB 2011-11-23 21:31 c791a6 id1928 1 20 GB 6.5 GB 0.0 MB 2011-11-25 16:39 c7a2a4 id1929 1 100 GB 66 GB 0.0 MB 2011-11-26 00:05 c7a457 id1935 1 100 GB 4.8 GB 0.0 MB 2011-11-29 20:00 caa616 id1931 1 60 GB 4.5 GB 0.0 MB 2011-11-27 21:26 caace2 id1908 1 20 GB 20 GB 0.0 MB 2011-11-11 16:53 cdba86 id1909 1 50 GB 17 GB 0.0 MB 2011-12-04 16:58 cdbc39 id1917 1 20 GB 18 GB 0.0 MB 2011-11-18 13:44 d0dc8e [root at alcor var]# collie vdi getattr thzhost lock VDI not found [root at alcor var]# collie vdi read thzhost Cannot get VDI info for thzhost 0 : No VDI found Failed to open VDI thzhost the other command about vdi remains the same for all vdi On Fri, Dec 16, 2011 at 04:35, MORITA Kazutaka <morita.kazutaka at lab.ntt.co.jp> wrote: > At Fri, 16 Dec 2011 04:31:53 +0700, > icez network wrote: >> >> when i shutdown the whole cluster and run only on server 172.16.0.12 >> it said the following when try 'collie vdi list' >> >> Failed to read object 80cdba8600000000 Waiting for other nodes to join cluster >> Failed to read inode header >> Failed to read object 80cdbc3900000000 Waiting for other nodes to join cluster >> Failed to read inode header >> Failed to read object 80d0d92800000000 Waiting for other nodes to join cluster >> Failed to read inode header >> Failed to read object 80d0dc8e00000000 Waiting for other nodes to join cluster >> Failed to read inode header >> Failed to read object 80e5729a00000000 Waiting for other nodes to join cluster >> Failed to read inode header >> Failed to read object 80fa0ac800000000 Waiting for other nodes to join cluster >> Failed to read inode header >> Failed to read object 80fe898600000000 Waiting for other nodes to join cluster >> Failed to read inode header >> >> >> $ collie cluster info >> Cluster status: Waiting for other nodes to join cluster > > Then, what happens if you add 172.16.0.11? > > What is the output of 'collie vdi list'? > > Thanks, > > Kazutaka -- Personal hosting by icez network http://www.thzhost.com |