search for: 350t

...ystem Size Used Avail Use% Mounted on /dev/sda1 59T 42T 17T 72% /bricks/data_A1 /dev/sdb1 59T 45T 14T 77% /bricks/data_A2 /dev/sdd1 59T 39M 59T 1% /bricks/data_A4 /dev/sdc1 59T 1.9T 57T 4% /bricks/data_A3 server-A:/dataeng 350T 83T 268T 24% /dataeng And on server-B: Filesystem Size Used Avail Use% Mounted on /dev/sdb1 59T 34T 25T 58% /bricks/data_B2 /dev/sdc1 59T 2.0T 57T 4% /bricks/data_B3 /dev/sdd1 59T 39M 59T 1% /bricks/data_B4 /dev/sda1 59T 38T...

...pdate to CentOS 7.4 and gluster 3.12.4, ?df? correctly showed the size for the volume as 233TB. After the update, we added 2 bricks with 1 on each server, but the output of ?df? still only listed 233TB for the volume. We added 2 more bricks, again with 1 on each server. The output of ?df? now shows 350TB, but the aggregate of 8 ? 59TB bricks should be ~466TB. > > Configuration 2: A distributed, replicated volume with 9 bricks on each server for a total of ~350TB of storage. After the server update to RHEL 6.9 and gluster 3.12.4, the volume now shows as having 50TB with ?df?. No changes wer...

...pdate to CentOS 7.4 and gluster 3.12.4, ?df? correctly showed the size for the volume as 233TB. After the update, we added 2 bricks with 1 on each server, but the output of ?df? still only listed 233TB for the volume. We added 2 more bricks, again with 1 on each server. The output of ?df? now shows 350TB, but the aggregate of 8 ? 59TB bricks should be ~466TB. Configuration 2: A distributed, replicated volume with 9 bricks on each server for a total of ~350TB of storage. After the server update to RHEL 6.9 and gluster 3.12.4, the volume now shows as having 50TB with ?df?. No changes were made to t...