search for: stor2

...ly going to be used to host the oVirt engine as a hypervisor (it will have Gluster volumes in the near future). I have three other servers I am using for storage. One of those three is also going to be a hypervisor and the other two are dedicated storage servers (Their names are GSA-Stor1 & GSA-Stor2). When I first deployed the engine, this server (GSAoV07) I'm having an issue with was in green status. I then added in the other server (I have it as GSAoV08), who is acting as both a Gluster server and a hypervisor. It had the red, downward arrow, for a while after I added it late at night. B...

...to host the oVirt engine as a hypervisor (it will have > Gluster volumes in the near future). I have three other servers I am using > for storage. One of those three is also going to be a hypervisor and the > other two are dedicated storage servers (Their names are GSA-Stor1 & > GSA-Stor2). > When I first deployed the engine, this server (GSAoV07) I?m having an > issue with was in green status. > I then added in the other server (I have it as GSAoV08), who is acting as > both a Gluster server and a hypervisor. It had the red, downward arrow, for > a while after I adde...

...ly going to be used to host the oVirt engine as a hypervisor (it will have Gluster volumes in the near future). I have three other servers I am using for storage. One of those three is also going to be a hypervisor and the other two are dedicated storage servers (Their names are GSA-Stor1 & GSA-Stor2). When I first deployed the engine, this server (GSAoV07) I?m having an issue with was in green status. I then added in the other server (I have it as GSAoV08), who is acting as both a Gluster server and a hypervisor. It had the red, downward arrow, for a while after I added it late at night. But,...

...pervisor (it will have >>> Gluster volumes in the near future). I have three other servers I am using >>> for storage. One of those three is also going to be a hypervisor and the >>> other two are dedicated storage servers (Their names are GSA-Stor1 & >>> GSA-Stor2). >>> When I first deployed the engine, this server (GSAoV07) I?m having an >>> issue with was in green status. >>> I then added in the other server (I have it as GSAoV08), who is acting >>> as both a Gluster server and a hypervisor. It had the red, downward arro...

...t engine as a hypervisor (it will have >> Gluster volumes in the near future). I have three other servers I am using >> for storage. One of those three is also going to be a hypervisor and the >> other two are dedicated storage servers (Their names are GSA-Stor1 & >> GSA-Stor2). >> When I first deployed the engine, this server (GSAoV07) I?m having an >> issue with was in green status. >> I then added in the other server (I have it as GSAoV08), who is acting as >> both a Gluster server and a hypervisor. It had the red, downward arrow, for >>...

...;>> (it will have Gluster volumes in the near future). I have three other >>>> servers I am using for storage. One of those three is also going to be a >>>> hypervisor and the other two are dedicated storage servers (Their names are >>>> GSA-Stor1 & GSA-Stor2). >>>> When I first deployed the engine, this server (GSAoV07) I?m having an >>>> issue with was in green status. >>>> I then added in the other server (I have it as GSAoV08), who is acting >>>> as both a Gluster server and a hypervisor. It had the re...

...ly going to be used to host the oVirt engine as a hypervisor (it will have Gluster volumes in the near future). I have three other servers I am using for storage. One of those three is also going to be a hypervisor and the other two are dedicated storage servers (Their names are GSA-Stor1 & GSA-Stor2). When I first deployed the engine, this server (GSAoV07) I?m having an issue with was in green status. I then added in the other server (I have it as GSAoV08), who is acting as both a Gluster server and a hypervisor. It had the red, downward arrow, for a while after I added it late at night. But,...

.../dev/sdb1 26T 1,1T 25T 4% /mnt/glusterfs/vol0 /dev/sdc1 50T 16T 34T 33% /mnt/glusterfs/vol1 stor1data:/volumedisk0 101T 3,3T 97T 4% /volumedisk0 stor1data:/volumedisk1 197T 61T 136T 31% /volumedisk1 [root at stor2 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 26T 1,1T 25T 4% /mnt/glusterfs/vol0 /dev/sdc1 50T 16T 34T 33% /mnt/glusterfs/vol1 stor2data:/volumedisk0 101T 3,3T 97T 4% /volumedisk0 stor2data:/volumedisk1...

...T 4% /mnt/glusterfs/vol0 > /dev/sdc1 50T 16T 34T 33% /mnt/glusterfs/vol1 > stor1data:/volumedisk0 > 101T 3,3T 97T 4% /volumedisk0 > stor1data:/volumedisk1 > 197T 61T 136T 31% /volumedisk1 > > > [root at stor2 ~]# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sdb1 26T 1,1T 25T 4% /mnt/glusterfs/vol0 > /dev/sdc1 50T 16T 34T 33% /mnt/glusterfs/vol1 > stor2data:/volumedisk0 > 101T 3,3T 97T 4% /volumedisk0 &...

...ng network with mtu 9000 and client is not (yet). The question I've got is this: Is it normal to see this kind of an output: gluster volume heal HA-100G-POC-PVE info Brick stor1:/exports/HA-100G-POC-PVE/100G/ /images/100/vm-100-disk-1.raw - Possibly undergoing heal Number of entries: 1 Brick stor2:/exports/HA-100G-POC-PVE/100G/ /images/100/vm-100-disk-1.raw - Possibly undergoing heal This happens pretty often but with different disk images on different replicated volumes. I mean I'm not sure if it is wrong or right, just curious of this. -- Best regards, Roman. -------------- next par...

Hi Nithya, My initial setup was composed of 2 similar nodes: stor1data and stor2data. A month ago I expanded both volumes with a new node: stor3data (2 bricks per volume). Of course, then to add the new peer with the bricks I did the 'balance force' operation. This task finished successfully (you can see info below) and number of files on the 3 nodes were very similar ....

Hi Jose, On 28 February 2018 at 22:31, Jose V. Carri?n <jocarbur at gmail.com> wrote: > Hi Nithya, > > My initial setup was composed of 2 similar nodes: stor1data and stor2data. > A month ago I expanded both volumes with a new node: stor3data (2 bricks > per volume). > Of course, then to add the new peer with the bricks I did the 'balance > force' operation. This task finished successfully (you can see info below) > and number of files on the 3...

...--------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 703964 16384.0PB 1475983 0 0 completed 64:37:55 stor2data 704610 16384.0PB 1475199 0 0 completed 64:31:30 stor3data 703964 16384.0PB 1475983 0 0 completed 64:37:55 volume rebalance: volumedisk1: success [root at sto...

...--------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 703964 16384.0PB 1475983 0 0 completed 64:37:55 stor2data 704610 16384.0PB 1475199 0 0 completed 64:31:30 stor3data 703964 16384.0PB 1475983 0 0 completed 64:37:55 volume rebalance: volumedisk1: success [root at sto...

...Inode Size : 512 > Disk Space Free : 35.0TB > Total Disk Space : 49.1TB > Inode Count : 5273970048 > Free Inodes : 5273123069 > ------------------------------------------------------------ > ------------------ > Brick : Brick stor2data:/mnt/glusterfs/vol1/brick1 > TCP Port : 49153 > RDMA Port : 0 > Online : Y > Pid : 13344 > File System : xfs > Device : /dev/sdc1 > Mount Options : rw,noatime > Inode Size : 512...

...c1 Mount Options : rw,noatime Inode Size : 512 Disk Space Free : 35.0TB Total Disk Space : 49.1TB Inode Count : 5273970048 Free Inodes : 5273123069 ------------------------------------------------------------------------------ Brick : Brick stor2data:/mnt/glusterfs/vol1/brick1 TCP Port : 49153 RDMA Port : 0 Online : Y Pid : 13344 File System : xfs Device : /dev/sdc1 Mount Options : rw,noatime Inode Size : 512 Disk Space Free : 35.0TB Total Dis...