The RedHat documentation has a good process on how to clean a unusable brick:
5.4.4. Cleaning An Unusable Brick If the file system associated with the brick cannot be reformatted, and the brick directory cannot be removed, perform the following steps: 1 Delete all previously existing data in the brick, including the .glusterfs subdirectory. 2 Run # setfattr -x trusted.glusterfs.volume-id brick and # setfattr -x trusted.gfid brick to remove the attributes from the root of the brick. 3 Run # getfattr -d -m . brick to examine the attributes set on the volume. Take note of the attributes. 4 Run # setfattr -x attribute brick to remove the attributes relating to the glusterFS file system. The trusted.glusterfs.dht attribute for a distributed volume is one such example of attributes that need to be removed. 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 Regards, Everton Brogliatto On Thu, Aug 31, 2017 at 2:56 PM, Everton Brogliatto <broglia...@gmail.com> wrote: > Hi Mabi, > > 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. > > However, the gluster documentation specifies that if the session is to be > permanently deleted, this is the command to use: > gluster volume geo-replication gv1 snode1::gv2 delete reset-sync-time > > https://gluster.readthedocs.io/en/latest/Administrator% > 20Guide/Geo%20Replication/#deleting-the-session > > Regards, > Everton Brogliatto > > > > > > > On Thu, Aug 31, 2017 at 12:15 AM, mabi <m...@protonmail.ch> wrote: > >> Hi, has anyone any advice to give about my question below? Thanks! >> >> >> >> -------- Original Message -------- >> Subject: Manually delete .glusterfs/changelogs directory ? >> Local Time: August 16, 2017 5:59 PM >> UTC Time: August 16, 2017 3:59 PM >> From: m...@protonmail.ch >> To: Gluster Users <gluster-users@gluster.org> >> >> Hello, >> >> I just deleted (permanently) my geo-replication session using the >> following command: >> >> gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-geo >> delete >> >> >> >> 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? >> >> Finally shouldn't the geo-replication delete command I used above delete >> these files automatically for me? >> >> Regards, >> Mabi >> >> >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users@gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-users >> > >
_______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users