[Bugs] [Bug 1267752] New: Unable to mount a replicated volume with 2 servers, one brick per server when only 1 server is powered on from having both off
bugzilla at redhat.com
bugzilla at redhat.com
Wed Sep 30 20:51:48 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1267752
Bug ID: 1267752
Summary: Unable to mount a replicated volume with 2 servers,
one brick per server when only 1 server is powered on
from having both off
Product: GlusterFS
Version: 3.7.4
Component: core
Assignee: bugs at gluster.org
Reporter: julien.langlois at gmail.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Description of problem:
I have 2 identical Ubuntu 14.04 x64 virtual machines running on a LAN. Both
systems are server and client for GlusterFS point of view.
The GlusterFS server has 1 replicated volume with one brick per server. Both
systems mounts the volume.
When I shutdown the 2 systems and start only one back, I am unable to mount the
volume. The volume is not started.
The problem exists >= 3.6
Tested versions:
* 3.4.2 Official upstart OK
* 3.4.7 PPA upstart OK
* 3.5.6 PPA upstart OK
* 3.6.6 PPA upstart NOK
* 3.7.4 PPA upstart, initscript NOK
How reproducible: always
Steps to Reproduce:
1. Install server 1
# add-apt-repository -y ppa:gluster/glusterfs-3.7
# apt-get update -y
# apt-get install -y glusterfs-server glusterfs-client
# mkdir -p /mnt/{data/gluster,gluster-volume1}
# gluster vol create vol1 node1:/mnt/data/gluster/vol1 force
# gluster vol start vol1
# echo "127.0.0.1:vol1 /mnt/gluster-volume1 glusterfs
defaults,_netdev,noauto 0 0" >> /etc/fstab
2. Install server 2
# add-apt-repository -y ppa:gluster/glusterfs-3.7
# apt-get update -y
# apt-get install -y glusterfs-server glusterfs-client
# mkdir -p /mnt/{data/gluster,gluster-volume1}
# gluster peer probe node1
# gluster volume add-brick vol1 replica 2 node2:/mnt/data/gluster/vol1
force
# echo "127.0.0.1:vol1 /mnt/gluster-volume1 glusterfs
defaults,_netdev,noauto 0 0" >> /etc/fstab
3. Shutdown the 2 servers
4. Boot the server 1 only
5. Try to mount the volume:
# mount /mnt/gluster-volume1
Actual results: the volume is not mounted. No glusterfsd process running. The
volume is not started
Expected results: the volume is mounted (works in 3.4 & 3.5)
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list