search for: 35t

...197T 61T 136T 31% /volumedisk1 [root at stor3 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 stor3data:/volumedisk0 101T 3,3T 97T 4% /volumedisk0 stor3data:/volumedisk1 197T 61T 136T 31% /volumedisk1 However I'm concerned because,...

...disk1 > > > [root at stor3 ~]# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 > /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 > /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 > /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 > stor3data:/volumedisk0 > 101T 3,3T 97T 4% /volumedisk0 > stor3data:/volumedisk1 > 197T 61T 136T 31% /volumedisk1 > > &...

...> [root at stor3 ~]# df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >> stor3data:/volumedisk0 >> 101T 3,3T 97T 4% /volumedisk0 >> stor3data:/volumedisk1 >> 197T 61T 136T 31% /vol...

...or3 ~]# df -h >>> Filesystem Size Used Avail Use% Mounted on >>> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >>> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >>> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >>> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >>> stor3data:/volumedisk0 >>> 101T 3,3T 97T 4% /volumedisk0 >>> stor3data:/volumedisk1 >>> 197T...

...t;>>> Filesystem Size Used Avail Use% Mounted on >>>> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >>>> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >>>> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >>>> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >>>> stor3data:/volumedisk0 >>>> 101T 3,3T 97T 4% /volumedisk0 >>>> stor3data:/volumedisk1 >>>>...

...t; Filesystem Size Used Avail Use% Mounted on >>>>> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >>>>> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >>>>> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >>>>> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >>>>> stor3data:/volumedisk0 >>>>> 101T 3,3T 97T 4% /volumedisk0 >>>>> stor3data:/volumedisk1 >>&...

So, when you add a log device to a pool, it initiates a resilver. What is it actually doing, though? Isn''t the slog a copy of the in-memory intent log? Wouldn''t it just simply replicate the data that''s in the other log, checked against what''s in RAM? And presumably there isn''t that much data in the slog so there isn''t that much to check? Or

Hi Jose, There is a known issue with gluster 3.12.x builds (see [1]) so you may be running into this. The "shared-brick-count" values seem fine on stor1. Please send us "grep -n "share" /var/lib/glusterd/vols/volumedisk1/*" results for the other nodes so we can check if they are the cause. Regards, Nithya [1] https://bugzilla.redhat.com/show_bug.cgi?id=1517260

Hi, Some days ago all my glusterfs configuration was working fine. Today I realized that the total size reported by df command was changed and is smaller than the aggregated capacity of all the bricks in the volume. I checked that all the volumes status are fine, all the glusterd daemons are running, there is no error in logs, however df shows a bad total size. My configuration for one volume:

Hi, As a next question to my building this server. I'm nogt able to get a full verbose dmesg. Probably because the kernelbuffer for it is too small. I know there used to be a kernel option to increase it. But I can not find it with the setting in NOTES or any other place I looked.... Is it still there? Thanx, --WjW

...]R95]3;W5R8V5?0U-!+U5S92!O M<FEG:6YA;"!#35E+(&-O;&]R<SH@(B530TE04$0Z($1&12!#35E+7T-302!5 M<V5?3W)I9VEN86PB#0HJ0UA?0S)$7T--64M3;W5R8V4@57-E7U-O=7)C95]# M4T$O57-E(%-O=7)C92!#4T$Z("(E4T-)4%!$.B!$1D4@0TU92U]#4T$@57-E M7T9I;&4B#0HJ0UA?0S)$7T--64M3;W5R8V4@4W=O<"]35T]0.B`B)5-#25!0 M1#H@1$9%($]-7U-O=7)C94--64L@4$)?4U=/4"(-"BI#6%]#,D1?0TU92U-O M=7)C92!&;V=R84=L;W-S+T9O9W)A($=L;W-S.B`B)5-#25!01#H@1$9%($]- M7U-O=7)C94--64L@4$)?1F]G<F%?1VQO<W,B#0HJ0UA?0S)$7T--64M3;W5R M8V4@1F]G<F%-871T+T9O9W)A($UA='0Z("(E4T-)4%!$.B!$1D4@3TU?4V]U M<...

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