[sheepdog-users] Fwd: dog vdi check: ovject is incosistent

[Micha Kersloot]

Hi, 

----- Original Message -----

> From: "Micha Kersloot" <micha at kovoks.nl>
> To: "Valerio Pachera" <sirio81 at gmail.com>
> Cc: "Lista sheepdog user" <sheepdog-users at lists.wpkg.org>
> Sent: Friday, October 3, 2014 12:27:55 PM
> Subject: Re: [sheepdog-users] Fwd: dog vdi check: ovject is incosistent

> Hi,

> ----- Original Message -----

> > From: "Valerio Pachera" <sirio81 at gmail.com>
> 
> > To: "Lista sheepdog user" <sheepdog-users at lists.wpkg.org>
> 
> > Sent: Friday, October 3, 2014 12:18:50 PM
> 
> > Subject: [sheepdog-users] Fwd: dog vdi check: ovject is incosistent
> 

> > 2014-10-03 10:35 GMT+02:00 Micha Kersloot < micha at kovoks.nl > :
> 

> > > Recovery kicked in and the VM continued. After recovery was complete, I
> > > tried
> > > to start the sheep daemon and that failed because of some journal errors.
> > > I
> > > added the 'skip' to the journal option and recovery kicked in again.
> > > Looked
> > > all fine to me!
> > 
> 

> > What version of sheepdog are you running?
> 
> > May you report the options you use to run sheep?
> 

> sheep -v
> Sheepdog daemon version 0.8.3

> /usr/sbin/sheep -y 10.10.0.30 -c
> zookeeper:10.10.0.21:2181,10.10.0.22:2181,10.10.0.30:2181 -j size=512M -w
> size=50G --upgrade --pidfile /var/run/sheepdog.pid /var/lib/sheepdog
> /mnt/sheep/30

> > > But... To be sure I did a dog vdi check and that gives me:
> > 
> 
> > > object 2e754900000844 is inconsistent
> > 
> 

> > Wow, I've never seen that.
> 
> > Did you shutdown the guest before running vdi check?
> 

> First the guest was running, then I shutdown the guest and that made no
> difference. Here is info about the vdi itself.

> dog vdi list
> Name Id Size Used Shared Creation time VDI id Copies Tag
> micha_test 0 10 GB 9.7 GB 0.0 MB 2014-10-02 17:36 2e7549 2:1

I've done some more reading and working with the cluster and decided using the object cache is maybe not the best solution in my situation. So I've shutdown the cluster with dog cluster shutdown, replaced the "-w size=50G" with "-n" on all nodes and restarted the cluster without any errors. Now I have major filesystem errors on the kvm guest, but dog vdi check now runs without any problems. To me it looks like there where problems with the VDI which are now corrected by sheepdog, but these corrections somehow corrupted the filesystem. So two things to do for me now. 1 testing of the current setup is more stable 2. Setting up a new cluster to see if I can reproduce the problems. 

Greets, 

Micha 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog-users/attachments/20141003/1382b181/attachment-0005.html>