From: Rafał Radecki <radecki.rafal@xxxxxxxxx>
> I have two servers ("master" and "slave") with a replicated
> gluster
> volume. Recently I've had a problem with slave and gluster does not
> work on it now.
> So I would like to:
> - stop and remove current volume on master (on slave it is not accessible);
> - stop gluster software on master (already stopped on slave);
> - remove gluster software on master and slave (previous administrator
> used own built rpms, I would like to use
> http://download.gluster.org/pub/gluster/glusterfs/3.3/3.3.1/EPEL.repo/);
> - clean old information:
> setfattr -x trusted.glusterfs.volume-id /gluster
> setfattr -x trusted.gfid /gluster
> rm -rf /gluster/.glusterfs
> - rsync data from master to slave;
> - start gluster and create a volume with data in rsynced /gluster directory.
> Are there any pitfalls I should know about?
I think you would have more answers on the glusterfs mailing list.
JD
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
