Displaying 6 results from an estimated 6 matches for "59t".
Did you mean:
59
2018 Jan 31
1
df does not show full volume capacity after update to 3.12.4
...df ?h output for all the bricks is ~163T. Close enough for me to believe everything is there. The total for used space in the df ?h of the mountpoint it 83T, roughly half what is used.
Relevant lines from df ?h on server-A:
Filesystem 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...
2018 Jan 31
0
df does not show full volume capacity after update to 3.12.4
...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 o...
2018 Jan 31
4
df does not show full volume capacity after update to 3.12.4
...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 o...
2019 May 06
1
dfree command cannot report correct disk space
Hi,
my filesystems is mounted like the below df output, /share is exported
in samba.
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 50G 9.1G 41G 19% /share
nfs1:/ 492T 433T 59T 89% /share/group1
If a 100G file is copied to /share/group1, samba will report the storage
doesn't have enough space.
I tried to use 'dfree command' to report a correct disk space, the thing
is dfree command always gets parameter $1 as '.', and its pwd is always
'/shar...
2017 Sep 28
1
upgrade to 3.12.1 from 3.10: df returns wrong numbers
...cks/sdg1
/dev/sdg1????????????????????????? 7.3T? 756G? 6.6T? 11% /bricks/sdg1
/dev/sdh1????????????????????????? 7.3T? 753G? 6.6T? 11% /bricks/sdh1
/dev/sdh1????????????????????????? 7.3T? 753G? 6.6T? 11% /bricks/sdh1
[root at st-srv-03 ~]# df -h|grep localhost
localhost:/test???????????????????? 59T? 5.7T?? 53T? 10% /gfs/test
localhost:/vm-images?????????????? 7.3T? 717G? 6.6T? 10% /gfs/vm-images
This is on CentOS 7.
Upgrade method was to shutdown glusterd/glusterfsd, "yum erase
centos-release-gluster310", "yum install centos-release-gluster312",
"yum upgrade -y&qu...
2008 Jun 30
4
Rebuild of kernel 2.6.9-67.0.20.EL failure
Hello list.
I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without
modifications.
How did I try it?
Created a (non-root) build environment (not a mock )
Installed the kernel.scr.rpm and did a
rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee
prep-out.log
The build failed at the end:
Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL
Checking