search for: 59tb

...y part of the available space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. We have 2 different server configurations. Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...for multi-brick volumes. All nodes are at 3.12.4. This occurs on both > servers and clients. > > > > We have 2 different server configurations. > > > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. > The initial configuration had 4 bricks of 59TB each with 2 on each server. > Prior to the update 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 bri...

...at 3.12.4. This occurs on both >> servers and clients. >> >> >> >> We have 2 different server configurations. >> >> >> >> Configuration 1: A distributed volume of 8 bricks with 4 on each server. >> The initial configuration had 4 bricks of 59TB each with 2 on each server. >> Prior to the update 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...

...space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. > > We have 2 different server configurations. > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...y part of the available space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. We have 2 different server configurations. Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...y part of the available space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. We have 2 different server configurations. Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...y part of the available space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. We have 2 different server configurations. Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...for multi-brick volumes. All nodes are at 3.12.4. This occurs on both > servers and clients. > > > > We have 2 different server configurations. > > > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. > The initial configuration had 4 bricks of 59TB each with 2 on each server. > Prior to the update 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 bri...

...y part of the available space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. We have 2 different server configurations. Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...for multi-brick volumes. All nodes are at 3.12.4. This occurs on both > servers and clients. > > > > We have 2 different server configurations. > > > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. > The initial configuration had 4 bricks of 59TB each with 2 on each server. > Prior to the update 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 bri...

...for multi-brick volumes. All nodes are at 3.12.4. This occurs on both > servers and clients. > > > > We have 2 different server configurations. > > > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. > The initial configuration had 4 bricks of 59TB each with 2 on each server. > Prior to the update 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 bri...

...for multi-brick volumes. All nodes are at 3.12.4. This occurs on both > servers and clients. > > > > We have 2 different server configurations. > > > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. > The initial configuration had 4 bricks of 59TB each with 2 on each server. > Prior to the update 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 bri...

...y part of the available space on the mount point for multi-brick volumes. All nodes are at 3.12.4. This occurs on both servers and clients. We have 2 different server configurations. Configuration 1: A distributed volume of 8 bricks with 4 on each server. The initial configuration had 4 bricks of 59TB each with 2 on each server. Prior to the update 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...

...for multi-brick volumes. All nodes are at 3.12.4. This occurs on both > servers and clients. > > > > We have 2 different server configurations. > > > > Configuration 1: A distributed volume of 8 bricks with 4 on each server. > The initial configuration had 4 bricks of 59TB each with 2 on each server. > Prior to the update 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 bri...