On 06/04/2012 07:15 PM, Amar Tumballi wrote:
Do you know if I'll be able to convert a distribute to
distribute-replicate this way?
1) delete the distribute volume
2) create a distribute-replicate volume
3) run the self-heal, which hopefully results in the data moved to the
other brick, *not*
Hi David
Thanks for clearing it up
With regards to the "self-heal":
find /mnt/gfstest -noleaf -print0 | xargs --null stat >/dev/null
a) I do this on the server(1|2|client|doesnt-matter) ? IF server1 is the
one with the latest copy of data
b) Would the self-heal i've been reading about in 3.3 no
On 06/04/2012 05:21 PM, David Coulson wrote:
Question (4.2)
-Is it safe to create a brick in a directory that already has files in
it ?
As long as you force a self-heal on it before you use it.
Do you know if I'll be able to convert a distribute to
distribute-replicate this way?
1) delet
On 6/4/12 4:05 AM, Jacques du Rand wrote:
HI Guys
This all applies to Gluster3.3
I love gluster but I'm having some difficulties understanding some
things.
1.Replication(with existing data):
Two servers in simple single brick replication. ie 1 volume (testvol)
-server1:/data/ && server2:/d
HI Guys
This all applies to Gluster3.3
I love gluster but I'm having some difficulties understanding some things.
1.Replication(with existing data):
Two servers in simple single brick replication. ie 1 volume (testvol)
-server1:/data/ && server2:/data/
-server1 has a few millions files in the /d
