[Bugs] [Bug 1161893] volume no longer available after update to 3.6.1

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1161893

Mauro M. <mm13 at ezplanet.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(mm13 at ezplanet.net |
                   |)                           |



--- Comment #5 from Mauro M. <mm13 at ezplanet.net> ---
Thank you for looking after this issue.
I no longer have the logs because in the haste of restoring service I did not
make a backup of the /var gluster directories and I recovered the data by
accessing directly the brick/volume directory on the most up to date node.
However I was able to reproduce the issue after I totally deleted glusterfs
packages and /var directories and I re-installed the packages as explained
above. 

To mount the filesystem I put an entry in /etc/fstab as specified by the
on-line manual:

node1:/gv_home /home glusterfs defaults,_netdev 0 0

I am not sure which protocol this would use. Is it fuse?

After re-installing 3.5.2 and recreating the replicated gv everything is
working fine again. I also modified my glusterfs-epel.repo path to pick only
3.5 updates and thus ignore 3.6.

My current configuration (use case) is a 2 nodes replica/mirror with node2
normally turned off. When I turn on node2 the volume is synchronized
automatically and I can then use node2 as a replacement of node1 that now can
be turned off. This works very well up to release 3.5.2.

I believe this can be easily reproduced as explained in my second message.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.