hast: can't restore after disk failure

[Mikolaj Golub]

On Wed, Jun 12, 2013 at 12:23:52AM +0400, Dmitry Morozovsky wrote:
> On Tue, 11 Jun 2013, Mikolaj Golub wrote:
> 
> > On Tue, Jun 11, 2013 at 12:40:08AM +0400, Dmitry Morozovsky wrote:
> > > On Mon, 10 Jun 2013, Mikolaj Golub wrote:
> > > 
> > > [snipall]
> > > 
> > > > > Jun 10 16:56:20 <console.info> cthulhu3 kernel: Jun 10 16:56:20 <daemon.err> 
> > > > > cthulhu3 hastd[765]: [d1] (secondary) Worker process exited ungracefully 
> > > > > (pid=14380, exitcode=66).
> > > > > 
> > > > > Any hints? Thanks!
> > > > 
> > > > Have you run hastctl create to initialize metadata?
> > > 
> > > Yes, but did it naively:
> > > 
> > > hastctl create d1
> > 
> > No errors?
> 
> no visible, but hast instance ungracefully exits
> 
> > > and status still reported 0 as provider size...
> > 
> > I assume /dev/ada1p1 is present and readable/writable?
> > 
> > Symptoms are like if it did not exist.
> 
> nope, it does:
> 
> root at cthulhu3:/# diskinfo /dev/ada1p1
> /dev/ada1p1     512     999654686720    1952450560      0       1048576 1936954 16      63
> root at cthulhu3:/# diskinfo /dev/ada0p1
> /dev/ada0p1     512     999653638144    1952448512      0       1048576 1936952 16      63
> 

Hm, looking in the source where this error is generated:

  cthulhu3 hastd[14379]: [d1] (secondary) Unable to read metadata from /dev/ada1p1: No such file or directory.

it looks like hastd successfully read metadata from disk but failed to
parse it (did not found an entry). This usually happens when metadata
is not initialized by `hastctl create`.

Does `hastctl dump d1' not work too?

-- 
Mikolaj Golub