[sheepdog] zookeeper quitting unexpectedly causes recoveringfromjournal file failed

[Hongyi Wang]

vdi check needs volume-id. How can I get the volume-id without the help of "vdi list"?
>collie vdi list
  Name        Id    Size    Used  Shared    Creation time   VDI id  Copies  Tag
Failed to read object 801d5fbd00000000 No object found
Failed to read inode header
Failed to read object 80791a2400000000 No object found
Failed to read inode header
Failed to read object 809133bf00000000 No object found
Failed to read inode header
Failed to read object 809133c000000000 No object found
Failed to read inode header
Failed to read object 80d322dd00000000 No object found
Failed to read inode header



 thanks,


--Hongyi
 
------------------ Original ------------------
From:  "Liu Yuan"<namei.unix at gmail.com>;
Date:  Thu, May 23, 2013 02:29 PM
To:  "Hongyi Wang"<hongyi at zelin.io>; 
Cc:  "sheepdog"<sheepdog at lists.wpkg.org>; "k"<k at zelin.io>; 
Subject:  Re: [sheepdog] zookeeper quitting unexpectedly causes recoveringfromjournal file failed

 
On 05/23/2013 02:25 PM, Hongyi Wang wrote:
> However, I found all the vdi are lost (All the node recovery has
> completed.). What happened? and how can I get my lost vdi?

All the vdi are lost? seems very fatal problem. Can vdi check work?

Thanks,
Yuan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20130523/2426ba4e/attachment-0004.html>