[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



--- Comment #1 from Mauro M. <mm13 at ezplanet.net> ---
I have done more tests as follows on two physical CentOS 6.6 x86_64 servers 
1) I erased all gluster packages and removed manually the directory that were
left over: /var/lib/glusterd and /var/log/glusterfs
2) I yum re-installed glusterfs packages 3.6.1 from glusterfs-epel.repo
glusterfs-fuse
glusterfs-libs
glusterfs-server
glusterfs-geo-replication
glusterfs-api
glusterfs
glusterfs-cli

3) I re-created the brick filesystems using mkfs.xfs -f -i size=512 [mydev] on
two nodes that here I will refer to as node1 and node2
4) I activated glusterd service using "chkconfig glusterd on" and I started
glusterd using "service glusterd start"
5) I created a volume following the exact instructions at 
http://www.gluster.org/community/documentation/index.php/QuickStart


6) I started and mounted the volume. So far so good
7) I set nfs.disable on for the volume since I have several nfs exported
filesystems and they would conflict
8) I included the volume mount in /etc/fstab as glusterfs
9) I filled the volume with some data
10) I shutdown node2
11) I shutdown node1 and then rebooted it (node1). node2 still shutdown
12) at boot "glusterd start" hung for several minutes thus hanging the whole
server boot process
13) once the server finally resumed booting, the gluster volume failed to mount
14) I tried to restart glusterd manually, still with the same results
15) I started node2, same situation on node2

------------------------

At this point I removed all gluster 3.6.1 packages and repeated the above
installing 3.5.2 packages instead.

With 3.5.2 I found no problem whatsoever, glusterd does not hang, filesystem
gets mounted, no matter if either one node is started at a time or both at the
same time. If I decide to leave node2 shutdown, when I boot it even after days
it re-synchronizes and everything works fine.

I would appreciate if this issue could be fixed for release 3.6.1 to support
the use cases perfectly working with releases up to 3.5.2.

I recommend as well to implement full regression testing before a new release.

THANK YOU.

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