On 15/05/2016 12:45 AM, Lindsay Mathieson wrote:
*First off I tried removing/adding a brick.*
gluster v remove-brick replica 2
vng.proxmox.softlog:/tank/vmdata/test1 force.
That worked fine, VM's (on another node) kept running without a hiccup
I deleted /tank/vmdata/test1, then
gluster v add-brick replica 3
vng.proxmox.softlog:/tank/vmdata/test1 force.
I tried this again but added a differently named brick (
vng.proxmox.softlog:/tank/vmdata/test1-2). Results were similar to
replace-brick, much less reverse heals, but still some (3 shards). There
was some corruption in the running VM's
--
Lindsay Mathieson
_______________________________________________
Gluster-users mailing list
[email protected]
http://www.gluster.org/mailman/listinfo/gluster-users
