Hi Sander,
Sorry for not getting back to you.
I guess, when you don’t use quota you do not need to run the scripts.
I do not have any experience changing the op-version on a running glusterfs
cluster. But looking at some threads, it should be possible to change it on a
running glusterfs
Jiri,
I’ve updated the op-version yesterday online without any problems, so I hope to
be able to migrate my old bricks to the new tomorrow night without hassle using
the remove brick command once all new bricks are added.
My new bricks are smaller than the current ones but higher in number so
Jiri,
thanks for the information, I just commented on a question about op-version….
I upgraded all systems to 3.6.2 does this mean they all will use the correct
op-version and will not revert to old style behaviour?
Met vriendelijke groet / kind regards,
Sander Zijlstra
| Linux Engineer |
LS,
I’m planning to decommission a few servers from my cluster, so to confirm:
Since version 3.6 the remove brick command migrates the data away from the
brick being removed, right?
When I have replicated bricks (replica 2), I also need to do remove brick
volume replica 2 brick1 brick2 …. ,
Hi Sander,
Since version 3.6 the remove brick command migrates the data away from the
brick being removed, right?
It should :)
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/pdf/Administration_Guide/Red_Hat_Storage-3-Administration_Guide-en-US.pdf
page 100, is I think a good
Jiri,
thanks, I totally missed the op-version part as it’s not mentioned in the
upgrade instructions as per the link you send. Actually I read that link and
because I do not use quota I didn’t use that script either.
Can I update the op-version when the volume is online and currently doing a
