On 29/11/2023 22:58 Diego Zuccato wrote:
>If the old volume is still online, it's better if you copy from its FUSE
mount point to the new one.
The old servers are offline and cannot be rebooted, but the bricks
themselves are running fine. The whole point of the exercise is to bring
the volumes
Much depends on the original volume layout. For replica volumes you'll
find multiple copies of the same file on different bricks. And sometimes
0-byte files that are placeholders of renamed files: do not overwrite a
good file with its empty version!
If the old volume is still online, it's
Ok, it's been a while, but I'm getting back to this "project".
I was unable to get gluster for the platform: the machines are ARM-based,
and there are no ARM binaries on the gluster package repo. I tried building
it instead, but the version of gluster I was running was quite old, and I
couldn't
You must have been running a really old version of glusterfs, 2 node
systems haven't been supported for a few major releases now. if you
want n-1 reliability you need at least a 4 node system.
On the bright side setup your new gluster system with approriate
storage. Gluster doesn't do anything
If you preserved the gluster structure in /etc/ and /var/lib, you should be
able to run the cluster again.First install the same gluster version all nodes
and then overwrite the structure in /etc and in /var/lib.Once you mount the
bricks , start glusterd and check the situation.
The other
