Bug 949096

Description of problem:

In a volume /w quorum enabled, I'd expect reads to fail when the available servers cannot form a quorum.

Version-Release number of selected component (if applicable):


How reproducible:

Every time.

Steps to Reproduce:

Run a script like:
gluster volume create vol1 replica 3 192.168.124.21:/mnt/bricks/vol1 192.168.124.22:/mnt/bricks/vol1  192.168.124.23:/mnt/bricks/vol1 
gluster volume set vol1 cluster.quorum-type auto
gluster volume start vol1

mkdir -p /mnt/vol1/
mount -t glusterfs 192.168.124.21:/vol1 /mnt/vol1
cd /mnt/vol1

echo "update 1" > test.txt
cat test.txt
ssh 192.168.124.21 service glusterd stop
echo "update 2" > test.txt
cat test.txt
ssh 192.168.124.21 service glusterd start
ssh 192.168.124.22 service glusterd stop
ssh 192.168.124.23 service glusterd stop
sleep 20
cat test.txt


Actual results:

Creation of volume vol1 has been successful. Please start the volume to access data.
Set volume successful
Starting volume vol1 has been successful
update 1
Redirecting to /bin/systemctl stop  glusterd.service
update 2
Redirecting to /bin/systemctl start  glusterd.service
Redirecting to /bin/systemctl stop  glusterd.service
Redirecting to /bin/systemctl stop  glusterd.service
update 1

Expected results:

Creation of volume vol1 has been successful. Please start the volume to access data.
Set volume successful
Starting volume vol1 has been successful
update 1
Redirecting to /bin/systemctl stop  glusterd.service
update 2
Redirecting to /bin/systemctl start  glusterd.service
Redirecting to /bin/systemctl stop  glusterd.service
Redirecting to /bin/systemctl stop  glusterd.service
cat: test.txt: Transport endpoint is not connected

Additional info: