The command I used for rebalance was "gluster volume rebalance data start", where data is the name of my volume
gluster volume status data
Status of volume: data
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick datanode01:/mnt/data/bricks/data 49152 0 Y 9849
Brick datanode02:/mnt/data/bricks/data 49152 0 Y 5466
Brick datanode03:/mnt/data/bricks/data 49152 0 Y 4040
Brick datanode04:/mnt/data/bricks/data 49152 0 Y 1879
Task Status of Volume data
------------------------------------------------------------------------------
Task : Rebalance
ID : 002eb0e7-9de7-45b8-b71b-d8aae4a2d292
Status : in progress
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick datanode01:/mnt/data/bricks/data 49152 0 Y 9849
Brick datanode02:/mnt/data/bricks/data 49152 0 Y 5466
Brick datanode03:/mnt/data/bricks/data 49152 0 Y 4040
Brick datanode04:/mnt/data/bricks/data 49152 0 Y 1879
Task Status of Volume data
------------------------------------------------------------------------------
Task : Rebalance
ID : 002eb0e7-9de7-45b8-b71b-d8aae4a2d292
Status : in progress
gluster volume info data
Volume Name: data
Type: Distribute
Volume ID: 294d95ce-0ff3-4df9-bd8c-a52fc50442ba
Status: Started
Snapshot Count: 0
Number of Bricks: 4
Transport-type: tcp
Bricks:
Brick1: datanode01:/mnt/data/bricks/data
Brick2: datanode02:/mnt/data/bricks/data
Brick3: datanode03:/mnt/data/bricks/data
Brick4: datanode04:/mnt/data/bricks/data
Options Reconfigured:
performance.cache-max-file-size: 128MB
performance.cache-size: 64GB
nfs.disable: on
performance.readdir-ahead: on
diagnostics.latency-measurement: on
diagnostics.count-fop-hits: on
cluster.min-free-disk: 10%
Volume Name: data
Type: Distribute
Volume ID: 294d95ce-0ff3-4df9-bd8c-a52fc50442ba
Status: Started
Snapshot Count: 0
Number of Bricks: 4
Transport-type: tcp
Bricks:
Brick1: datanode01:/mnt/data/bricks/data
Brick2: datanode02:/mnt/data/bricks/data
Brick3: datanode03:/mnt/data/bricks/data
Brick4: datanode04:/mnt/data/bricks/data
Options Reconfigured:
performance.cache-max-file-size: 128MB
performance.cache-size: 64GB
nfs.disable: on
performance.readdir-ahead: on
diagnostics.latency-measurement: on
diagnostics.count-fop-hits: on
cluster.min-free-disk: 10%
On my client machine, this is the glusterfs mounted (same size results no matter which node I mount)
192.0.2.110:/data 230T 178T 52T 78% /mnt/dataRusty
On Sun, Oct 18, 2020 at 11:03 PM Strahil Nikolov <hunter86_bg@xxxxxxxxx> wrote:
Hi Rusty,
please provide more details like:
gluster volume status VOL
gluster volume info VOL
and from the client:
df -h /path/to/mounted/volume
P.S.: What was the command you used to add and then rebalance the volume ?
Best Regards,
Strahil Nikolov
В понеделник, 19 октомври 2020 г., 05:36:20 Гринуич+3, Rusty Bower <rusty@xxxxxxxxxxxxxx> написа:
Hey all,
I just added a new brick to my volume (currently in a rebalance), but the increased data size doesn't show when mounting the volume from another node. I searched through the mailing list, but didn't see any pointers. Does a rebalance need to finish before the additional volume will show in remote mounts?
Rusty
________
Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
