[Gluster-users] Volume ID mismatch for brick after extending LVM
Urgen Sherpa
norbuurgen at gmail.com
Wed Jun 24 05:51:18 UTC 2015
Hello,
for testing and scaling purpose i gave it a try with 2 ubuntu 14.04
machines on vmware workstation.i installed glusterfs 3.5 on both of them. i
started out by creating identical LVM on both of them,formatted with XFS
and created replicated volumes
#gluster volume create gvola replica 2 gluster1:/public/sdb1/brick/
gluster2:/public/sdb1/brick/
i mounted them on (the same 2)both servers and were working (replication
was fine). Problem arised when additional disks were added/extended to LVM.
i extended the lvm and did "xfsgrow" on both nodes and when i tried to stop
and start volume . this error showed up
volume start: gvola: failed: Volume id mismatch for brick
gluster1:/public/sdb1/brick. Expected volume id
fca40349-5fc6-4974-a7b7-a2f3d560f41b, volume id
c29b0f57-c018-4d4e-9bdc-2dda6f122dfc found
what do you suggest?
Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150624/a6b5c0e3/attachment.html>
More information about the Gluster-users
mailing list