In my experience .glusterfs is easily recoverable by going to the
brick path (if you have files there) and running stat for each object
but through mount point, something like:
cd BRICKPATH
sudo find . -path ./.glusterfs -prune -o -exec stat 'MUNTPATH/{}' \;
for example, if you need to recreate or create another volume - delete
.glusterfs and reset brick folder attr, and proceed with below trick
export brick_path=/main/brick4/geo0
sudo setfattr -x trusted.glusterfs.volume-id $brick_path
sudo setfattr -x trusted.gfid $brick_path
sudo rm -rf $brick_path/.glusterfs
files go nowhere - and they are everywhere you replicate them with Gluster
On Wed, Jan 24, 2018 at 3:44 PM, César E. Portela
<cportela@xxxxxxxxxxxxxx> wrote:
> Hi All,
>
> I have two glusterfs servers and doing the backup of these is very slow,
> when it does not fail.
> I have thousand and thousand and thousand files...
>
> Apparently the directory .glusterfs has some responsibility for the backup
> failure.
>
> Is necessary to make a backup of the .glusterfs directory?
>
> Thanks in advance.
>
>
> --
> Cease
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
