If you're not sure just pick one and save the other.
Steps I did:
save one of the qcow2 file split-brains (copy from brick to another name)
removed the qcow2 file that you just "backed up". Gluster will heal with
the other one.
restart VM
if VM recorvers after a fsck then just delete the saved qco
thanks
but which qcow2/FVM file choose for deletion? maybe there is some
known current best-practice for the VM maximum stability
if the VM is frozen the decision maybe to delete the oldest qcow2/FVM
file, or random choose if there is no difference
best regards,
--joão
Em 05-03-2014
I followed this blog: http://geekshell.org/~pivo/glusterfs-split-brain.html
(this can take too long because of using "find" if you have many files)
Right after Joe Julian released a pretty handy system for exploring the
split brains and fixing. You can check it out here:
http://joejulian.name/blog
hello Bryan and thanks for sharing!
how did you fix those 2 files on a split-brain situation? deleted one
"bad" file?
which one to select for deletion?
on an software update situation I would expect not to have peer probe
problems, simply because there are no "gluster peer probe" commands. T
I just did this last week from 3.3.0->3.4.2.
I never got the peer probe problems - but I did end up with 2 files being
in a split-brain situation.
Note: I only had ~hundred files that are qcow2 for KVM, so 2 files getting
split-brain is about 2% filesystem problem.
On Tue, Mar 4, 2014 at 1:43 A
Hello all
anyone tried a rolling upgrades with no downtime [1] from 3.3.0 to
3.4.2 or similar upgrade? any comments?
for testing purposes we've installed a 3.4.2 server and it won't peer,
giving the error "peer probe: failed: Peer X does not support required
op-version".
I guess this is e
