I was hoping for guidance on what is the best practice to deleting a
gluster volume?
I thought about it in 2 ways.
1. delete the content's of a volume through a client.
a. then stopping the gluster volume
b. delete the volume from the gluster cli
b. delete the volume dir
Some of the other 'linkto' files do point to the correct location
though.. I guess I should not delete those :)
v
On Tue 04 Mar 2014 09:28:39, Viktor Villafuerte wrote:
> Also I should say that all bricks still have plenty of free space, but
> there were network problems in the LAB..
>
>
> On
I've found this
[r...@gluster01.uat ~]# getfattr -dm . Alien3_1992_25_HLS_layer2_642000_282.ts
getfattr: Removing leading '/' from absolute path names
# file:
# Alien3_1992_25_HLS_layer2_642000_282.ts
trusted.gfid="��\012�h�Bȹ!v�/�,�"
trusted.glusterfs.dht.linkto="cdn-uat-replicate-0"
[r...@glus
Also I should say that all bricks still have plenty of free space, but
there were network problems in the LAB..
On Tue 04 Mar 2014 09:26:23, Viktor Villafuerte wrote:
> I've found this
>
> [r...@gluster01.uat ~]# getfattr -dm .
> Alien3_1992_25_HLS_layer2_642000_282.ts
> getfattr: Removing lea
Hello,
i asked myself if i run fix-layout and or rebalance if i could still mount the volume and write on it, or if it leads to an split-brain or something like this? I could not find an info on helpsite. I also read somewhere on the redhat sites that rebalance ist depreciated after adding a br