<div dir="ltr"><div class="gmail_default" style=""><font face="verdana, sans-serif">Thanks for the response Talur. I will really appreciate if you already have the steps for cleaning up the setup so i could start afresh.</font></div><div class="gmail_default" style=""><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style=""><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style=""><font face="verdana, sans-serif">Regards,</font></div><div class="gmail_default" style=""><font face="verdana, sans-serif" style="">Gaurav</font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-size:12.8px;font-family:arial,sans-serif"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 28, 2017 at 5:36 PM, Raghavendra Talur <span dir="ltr"><<a href="mailto:rtalur@redhat.com" target="_blank">rtalur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Sep 27, 2017 at 11:27 PM, Gaurav Chhabra<br>
<<a href="mailto:varuag.chhabra@gmail.com">varuag.chhabra@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
><br>
> I tried setting up Gluster cluster on Google cloud. It went fine. I always<br>
> stop the test instances when not in use. One day, when i started my Gluster<br>
> instances, few bricks went offline and i tried bringing them up but i<br>
> couldn't. I then tried removing the volumes but it gave me error related to<br>
> "device in use" and i think i also saw "bricks in use" messages. I tried<br>
> removing bricks but i couldn't. I finally thought of removing the extra raw<br>
> disks from all nodes that i initially added. But i guess Heketi was unable<br>
> to forget its past. I finally had to discard all the machines and created a<br>
> fresh three node cluster. :( All i wanted was to have a clean slate to start<br>
> with. In next two-three days, i will be starting with the actual setup on<br>
> live environment and using it for managing Kubernetes. Though in that case,<br>
> i will not be shutting down the cluster when not in use :) but i am<br>
> wondering if there is a way of resetting all things (bricks, volumes,<br>
> devices, nodes) in Gluster and Heketi, if such case arises, so i could start<br>
> afresh with the Heketi setup. Data backup is not a concern here as i am<br>
> considering this scenario only during the initial setup phase.<br>
><br>
><br>
> Regards,<br>
> Gaurav<br>
><br>
<br>
</div></div>Heketi does provide you mechanism to disable and remove devices/nodes.<br>
Once that is performed you can delete them. Yes, it is a iterative<br>
process at the end of which you will be left with nothing in topology.<br>
<br>
One thing to note is that you need to clean the disks of partition<br>
info for heketi to reuse them.<br>
<br>
Also, everything that heketi knows is in the db. If you delete the db<br>
file you have essentially created a fresh heketi instance. You will<br>
still have to clean the disks and gluster information though.<br>
<br>
Let us know if you are looking for a step by step guide to get this done.<br>
<br>
Talur<br>
<br>
> ______________________________<wbr>_________________<br>
> heketi-devel mailing list<br>
> <a href="mailto:heketi-devel@gluster.org">heketi-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/heketi-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/heketi-devel</a><br>
><br>
</blockquote></div><br></div>