After the self heal finishes it sort of works. Usually this destroys InnoDB if you're running a database. Most often, though, it also causes some libraries and similar to not be properly read in by the VM guest which means you have to reboot it to fix for this. It should be fairly easy to reproduce... just shut down a storage brick (any configuration... it doesn't seem to matter). Make sure of course that you have a running VM guest (KVM, etc) using the gluster mount. You'll then turn off(unplug, etc.) one of the storage bricks and wait a few minutes... then re-enable it. Justice London jlondon at lawinfo.com -----Original Message----- From: Tejas N. Bhise [mailto:tejas at gluster.com] Sent: Thursday, April 15, 2010 7:41 PM To: Justice London Cc: gluster-users at gluster.org Subject: Re: Self heal with VM Storage Justice, Thanks for the description. So, does this mean that after the self heal is over after some time, the guest starts to work fine ? We will reproduce this inhouse and get back. Regards, Tejas. ----- Original Message ----- From: "Justice London" <jlondon at lawinfo.com> To: "Tejas N. Bhise" <tejas at gluster.com> Cc: gluster-users at gluster.org Sent: Friday, April 16, 2010 1:18:36 AM Subject: RE: Self heal with VM Storage Okay, but what happens on a brick shutting down and being added back to the cluster? This would be after some live data has been written to the other bricks.
