[Bugs] [Bug 1274485] Unable to mount volume after conversion from distributed to replicated.

[bugzilla at redhat.com]

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



--- Comment #5 from Richard <redhat.bugs at pointb.co.uk> ---
Yes. If the volume is originally created as a 2 brick replciated volume then it
remounts just fine with only one brick online after poweroff.

However, if I create a volume with a single brick and then add a 2nd brick and
make the volume replicated I have issues remouting after reboot. I can mount
the replicated volume during this time, but after a reboot it is not mountable
again.

Yes, the steps you describe are pretty much what I use to create my volume.


1. Create a distributed volume in 1 node
1.1 Mount volume works
2. Add a peer
3. Add brick with the new brick been hosted in the newly added peer
3.1 mount volume on new brick works ok too.
4. Both nodes are powered off
5. One of the node comes back, glusterD service is up as well
6. Mount fails

Step #1) gluster volume create data brick2:folder
Step #3) gluster volume add-brick data replica 2 brick2:folder

my mount command is the standard fuse one:

mount -t glusterfs brick1:data /mnt/gluster

Thanks

Rich

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