search for: stor3data

...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 stor1 ~]# gluster volume rebalance volumedisk0 status Node Rebalanced-files size scanned failur...

...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 stor1 ~]# gluster volume rebalance volumedisk0 status Node Rebalanced-files size scanned failur...

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 . For volumedisk1 I only have files of 500MB and they are continuosl...

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 nodes were very similar . > > For volumedisk1 I only have files of...

...e% Mounted on /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 stor3data:/volumedisk0 101T 3,3T 97T 4% /volumedisk0 stor3data:/volumedisk1 197T 61T 136T 31% /volumedisk1 However I'm concerned because, as you can see, the volumedisk0 on stor3data is composed by 2 bricks on thesame disk but on different partitions...

...db1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 > /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 > /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 > /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 > stor3data:/volumedisk0 > 101T 3,3T 97T 4% /volumedisk0 > stor3data:/volumedisk1 > 197T 61T 136T 31% /volumedisk1 > > > However I'm concerned because, as you can see, the volumedisk0 on > stor3data is composed by 2 bricks on thesame...

...c1 Mount Options : rw,noatime Inode Size : 512 Disk Space Free : 35.0TB Total Disk Space : 49.1TB Inode Count : 5273970048 Free Inodes : 5273124718 ------------------------------------------------------------------------------ Brick : Brick stor3data:/mnt/disk_c/glusterfs/vol1/brick1 TCP Port : 49154 RDMA Port : 0 Online : Y Pid : 17439 File System : xfs Device : /dev/sdc1 Mount Options : rw,noatime Inode Size : 512 Disk Space Free : 35.7TB Total...

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