On 01/02/17 19:30, lejeczek wrote:
On 01/02/17 14:44, Atin Mukherjee
wrote:
To prove you have hit the same problem can you please
confirm the following:
1. Which Gluster version are you running?
2. Was any of the existing brick down?
2. Did you mounted the volume? If not you have two ways
(1) bring up the brick and restart glusterd followed by
add-brick or (2) if the existing brick(s) is bad for some
reason, restarting glusterd and mounting the volume followed
by a look up and then attempting add-brick should succeed.
a chance to properly investigate it has been lost I think.
I all started with one peer I missed was not migrated from 3.7 to
3.8 and unfortunately it was a system I could not tamper with
until late evening, which is now.
This problem though occurred after I already upgraded that gluster
to 3.8. I even removed that failing node's bricks and detached it,
re-attached it and still, those errors I described earlier...
until now when I restarted that one last one peer... now all seems
ok, well, at least I don't see those errors any more.
Should I now be looking at something particular more closely?
b.w.
L.
I realized I might have not been clear there, that box where I
missed that upgrade 3.7->3.8 was not the one where problem
existed, it was a different box, if that changes/helps anything.
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
