Displaying 8 results from an estimated 8 matches for "stor2data".
Did you mean:
stor1data
2018 Feb 28
2
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
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 .
Fo...
2018 Mar 01
2
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
...--------- ----------- -----------
----------- ----------- ----------- ------------
--------------
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 ~...
2018 Mar 01
0
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
...--------- ----------- -----------
----------- ----------- ----------- ------------
--------------
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 ~...
2018 Mar 01
0
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
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 node...
2018 Feb 28
2
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
...lumedisk0
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
197T 61T 136T 31% /volumedisk1
[root at stor3 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/...
2018 Feb 28
0
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
...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
> 197T 61T 136T 31% /volumedisk1
>
>
> [root at stor3 ~]# df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/sdb1 25T 6...
2018 Feb 27
2
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
...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 Disk Sp...
2018 Feb 28
0
df reports wrong full capacity for distributed volumes (Glusterfs 3.12.6-1)
...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
>...