Hi.
If you can still move files from the broken *volume*, you don't have to
touch .glusterfs folder: it's managed by gluster itself and that's the
preferred way to recover (more like a transfer between two volumes that
only accidentally share the filesystem on the bricks).
But if the vol was
Hi,
now i am a bit confused and dont know what to do?!
Situation: brocken distributed vol1 with two servers/bricks. I cant start the
volume, but i have access at the storage in which the files are.
Situation2: i created a new distributed vol2 over same two servers/bricks. i
mounted the new vol2
I searched the net but found any needfull, which helped. After one Brick OS is
complete crushing, to reinstall the os and glusterfs and try to reuse the
vol1.Readd the volume didnt work, so i decided to migrate to a new working
distributed vol2.
No i mounted new distributed vol2 on both server,
