because the files
wouldn’t be where they were supposed to be while it was working on rebalancing.
I took the route of taking the whole cluster down, making the modifications to
the vol info on each member, then bringing it all back up.
From: Brandon Mackie
Sent: April 21, 2014 1:24 PM
To: gluster
and
see if that corrects it as it does correct it on some test servers.
From: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] On Behalf Of Brandon Mackie
Sent: April 21, 2014 1:13 PM
To: gluster-users@gluster.org
Subject: Re: [Gluster-users] Upgrade from 3.3 to 3.4.3
still see it as rejected.
From: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] On Behalf Of Brandon Mackie
Sent: April 21, 2014 12:40 PM
To: gluster-users@gluster.org
Subject: [Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks
Good afternoon folks,
Not
Good afternoon folks,
Not sure if this is an occurrence of
https://bugzilla.redhat.com/show_bug.cgi?id=1072720 but cannot add new bricks
to my existing cluster running under Ubuntu 12. New bricks are completely blank.
Peer probed new from a trusted member. Both sides say “Peer Rejected
(Connec
