search for: disk_d

...Size Used Avail Use% 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 bu...

...tio on som3data differs too much (1TB): Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdc1 52737613824 15479191748 37258422076 30% /mnt/disk_c/glusterfs/vol1 -> stor3data /dev/sdd1 52737613824 15566398604 37171215220 30% /mnt/disk_d/glusterfs/vol1 -> stor3data Thinking in inodes: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdc1 5273970048 851053 5273118995 1% /mnt/glusterfs/vol1 -> stor1data /dev/sdc1 5273970048 849388 5273120660 1% /mnt/gl...

...Use% 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 c...

...ch (1TB): > Filesystem 1K-blocks Used Available > Use% Mounted on > /dev/sdc1 52737613824 15479191748 37258422076 30% > /mnt/disk_c/glusterfs/vol1 -> stor3data > /dev/sdd1 52737613824 15566398604 37171215220 30% > /mnt/disk_d/glusterfs/vol1 -> stor3data > > Thinking in inodes: > > Filesystem Inodes IUsed IFree IUse% > Mounted on > /dev/sdc1 5273970048 851053 5273118995 1% > /mnt/glusterfs/vol1 -> stor1data > /dev/sdc1 527397...

...ystem 1K-blocks Used Available >> Use% Mounted on >> /dev/sdc1 52737613824 15479191748 37258422076 30% >> /mnt/disk_c/glusterfs/vol1 -> stor3data >> /dev/sdd1 52737613824 15566398604 37171215220 30% >> /mnt/disk_d/glusterfs/vol1 -> stor3data >> >> Thinking in inodes: >> >> Filesystem Inodes IUsed IFree IUse% >> Mounted on >> /dev/sdc1 5273970048 851053 5273118995 1% >> /mnt/glusterfs/vol1 -> stor1data >&...

...s : rw,noatime Inode Size : 512 Disk Space Free : 35.7TB Total Disk Space : 49.1TB Inode Count : 5273970048 Free Inodes : 5273125437 ------------------------------------------------------------------------------ Brick : Brick stor3data:/mnt/disk_d/glusterfs/vol1/brick1 TCP Port : 49155 RDMA Port : 0 Online : Y Pid : 17459 File System : xfs Device : /dev/sdd1 Mount Options : rw,noatime Inode Size : 512 Disk Space Free : 35.6TB Total Disk Space...

...eer probe stor3data gluster volume add-brick volumedisk0 stor3data:/mnt/disk_b1/glusterfs/vol0 gluster volume add-brick volumedisk0 stor3data:/mnt/disk_b2/glusterfs/vol0 gluster volume add-brick volumedisk1 stor3data:/mnt/disk_c/glusterfs/vol1 gluster volume add-brick volumedisk1 stor3data:/mnt/disk_d/glusterfs/vol1 gluster volume rebalance volumedisk0 start force gluster volume rebalance volumedisk1 start force For some reason , could be unbalanced the assigned range of DHT for stor3data bricks ? Could be minor than stor1data and stor2data ? , Any way to verify it ? Any way to modify/rebal...

...: 512 > Disk Space Free : 35.7TB > Total Disk Space : 49.1TB > Inode Count : 5273970048 > Free Inodes : 5273125437 > ------------------------------------------------------------ > ------------------ > Brick : Brick stor3data:/mnt/disk_d/glusterfs/vol1/brick1 > TCP Port : 49155 > RDMA Port : 0 > Online : Y > Pid : 17459 > File System : xfs > Device : /dev/sdd1 > Mount Options : rw,noatime > Inode Size : 512 > Dis...