<div dir="ltr"><div><div>The RedHat documentation has a good process on how to clean a unusable brick:<br><br>5.4.4. Cleaning An Unusable Brick<br>If the file system associated with the brick cannot be reformatted, and the brick directory cannot be removed,<br>perform the following steps:<br>1 Delete all previously existing data in the brick, including the .glusterfs subdirectory.<br><br>2 Run<br> # setfattr -x trusted.glusterfs.volume-id brick<br> and <br> # setfattr -x trusted.gfid brick<br> to remove the attributes from the root of the brick.<br><br>3 Run <br> # getfattr -d -m . brick<br> to examine the attributes set on the volume. Take note of the attributes.<br><br>4 Run <br> # setfattr -x attribute brick<br> to remove the attributes relating to the glusterFS file system.<br> The trusted.glusterfs.dht attribute for a distributed volume is one such example of attributes that need to be removed.<br><br><br><a href="https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/pdf/administration_guide/Red_Hat_Gluster_Storage-3.2-Administration_Guide-en-US.pdf#%23Formatting_and_Mounting_Bricks-Reusing_a_brick">https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/pdf/administration_guide/Red_Hat_Gluster_Storage-3.2-Administration_Guide-en-US.pdf#%23Formatting_and_Mounting_Bricks-Reusing_a_brick</a><br><br></div>Regards,<br></div>Everton Brogliatto<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 31, 2017 at 2:56 PM, Everton Brogliatto <span dir="ltr"><<a href="mailto:brogliatto@gmail.com" target="_blank">brogliatto@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi Mabi,<br><br></div>If you will not use that geo-replication volume session again, I believe it is safe to manually delete the files in the brick directory using rm -rf.</div><div><br></div><div>However, the gluster documentation specifies that if the session is to be permanently deleted, this is the command to use:</div><div><code>gluster volume geo-replication
gv1 snode1::gv2 delete reset-sync-time</code></div><div><br></div><div></div><div><a href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Geo%20Replication/#deleting-the-session" target="_blank">https://gluster.readthedocs.<wbr>io/en/latest/Administrator%<wbr>20Guide/Geo%20Replication/#<wbr>deleting-the-session</a></div><div><br></div><div>Regards,</div><div>Everton Brogliatto<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Thu, Aug 31, 2017 at 12:15 AM, mabi <span dir="ltr"><<a href="mailto:mabi@protonmail.ch" target="_blank">mabi@protonmail.ch</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div>Hi, has anyone any advice to give about my question below? Thanks!<br></div><div class="m_8442997064559535177m_-5268083698901479548protonmail_signature_block m_8442997064559535177m_-5268083698901479548protonmail_signature_block-empty"><div class="m_8442997064559535177m_-5268083698901479548protonmail_signature_block-user m_8442997064559535177m_-5268083698901479548protonmail_signature_block-empty"><div><br></div></div><div class="m_8442997064559535177m_-5268083698901479548protonmail_signature_block-proton m_8442997064559535177m_-5268083698901479548protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote class="m_8442997064559535177m_-5268083698901479548protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: Manually delete .glusterfs/changelogs directory ?<br></div><div>Local Time: August 16, 2017 5:59 PM<br></div><div>UTC Time: August 16, 2017 3:59 PM<br></div><div>From: <a href="mailto:mabi@protonmail.ch" target="_blank">mabi@protonmail.ch</a><br></div><div>To: Gluster Users <<a href="mailto:gluster-users@gluster.org" target="_blank">gluster-users@gluster.org</a>><br></div><div><br></div><div>Hello,<br></div><div><br></div><div>I just deleted (permanently) my geo-replication session using the following command:<br></div><div><br></div><div>gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-g<wbr>eo delete<br></div><div class="m_8442997064559535177m_-5268083698901479548protonmail_signature_block m_8442997064559535177m_-5268083698901479548protonmail_signature_block-empty"><div class="m_8442997064559535177m_-5268083698901479548protonmail_signature_block-user m_8442997064559535177m_-5268083698901479548protonmail_signature_block-empty"><div><br></div></div><div class="m_8442997064559535177m_-5268083698901479548protonmail_signature_block-proton m_8442997064559535177m_-5268083698901479548protonmail_signature_block-empty"><br></div></div><div><br></div><div>and noticed that the .glusterfs/changelogs on my volume still exists. Is it safe to delete the whole directly myself with "rm -rf .glusterfs/changelogs" ? As far as I understand the CHANGELOG.* files are only needed for geo-replication, correct?<br></div><div><br></div><div>Finally shouldn't the geo-replication delete command I used above delete these files automatically for me?<br></div><div><br></div><div>Regards,<br></div><div>Mabi<br></div></blockquote><div><br></div><br></div></div>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br></blockquote></div><br></div>
</blockquote></div><br></div>