Displaying 14 results from an estimated 14 matches for "350tb".
Did you mean:
350kb
2018 Jan 31
4
df does not show full volume capacity after update to 3.12.4
...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 th...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.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...
2018 Jan 31
1
df does not show full volume capacity after update to 3.12.4
....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...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.4
...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...
2018 Jan 31
1
df does not show full volume capacity after update to 3.12.4
...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 th...
2018 Jan 31
2
df does not show full volume capacity after update to 3.12.4
...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 th...
2018 Jan 31
2
df does not show full volume capacity after update to 3.12.4
...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 th...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.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...
2018 Jan 31
4
df does not show full volume capacity after update to 3.12.4
...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 th...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.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...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.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...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.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...
2018 Jan 31
3
df does not show full volume capacity after update to 3.12.4
...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 th...
2018 Feb 01
0
df does not show full volume capacity after update to 3.12.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...