Yes, But I thought that cockpit should prevent creation of the gluster volume 'engine' as it is too small. @Dev Do we have such control ? Best Regards, Strahil Nikolov On Jul 8, 2019 09:19, Parth Dhanjal <dparth@redhat.com> wrote:
Hey!
The other 2 bricks were of 50G each. I forgot to check that. Sorry for the confusion. Thanks!
On Mon, Jul 8, 2019 at 11:42 AM Sahina Bose <sabose@redhat.com> wrote:
On Mon, Jul 8, 2019 at 11:40 AM Parth Dhanjal <dparth@redhat.com> wrote:
Hey!
I used cockpit to deploy gluster. And the problem seems to be with 10.xx.xx.xx9:/engine 50G 3.6G 47G 8% /rhev/data-center/mnt/glusterSD/10.70.41.139:_engine
Engine volume has 500G available Filesystem Size Used Avail Use% Mounted on /dev/mapper/gluster_vg_sdb1-gluster_lv_engine 500G 37M 500G 1% /gluster_bricks/engine
Check that you have 500G on all the bricks of the volume if you're using replica 3. It takes the minimum of the 3 bricks.
On Fri, Jul 5, 2019 at 8:05 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Parth,
did you use cockpit to deploy the gluster volume ? it's interesting why the cockpit allowed the engine's volume to be so small ...
Best Regards, Strahil Nikolov
В петък, 5 юли 2019 г., 10:17:11 ч. Гринуич-4, Simone Tiraboschi <stirabos@redhat.com> написа:
On Fri, Jul 5, 2019 at 4:12 PM Parth Dhanjal <dparth@redhat.com> wrote:
Hey!
I'm trying to deploy a 3 node cluster with gluster storage. After the gluster deployment is completed successfully, the creation of storage domain fails during HE deployment giving the error:
participants (1)
-
Strahil