Re: [Gluster-devel] [Gluster-users] Fw: Distributed-Disperse Shard Behavior

2022-02-09 Thread Fox
This appears to be exactly the issue. After testing with xfs mounted with the option 'allocsize=64k' and even trying ext4, the extraneous filesystem usage disappears. Removing 'allocsize=64k' returns the additional space usage. The linked article also makes reference to

[Gluster-devel] [Smallfile-Replica-3] Performance report for Gluster Upstream - 10/02/2022 Test Status: PASS (0.00%)

2022-02-09 Thread Gluster-jenkins
final.csv Description: Binary data --- Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Coverity Warning Alert

2022-02-09 Thread sajmoham
Current Threshold: 16. Coverity Warning Latest Count: 20 --- Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] [Gluster-users] Fw: Distributed-Disperse Shard Behavior

2022-02-09 Thread Xavi Hernandez
Hi, this problem is most likely caused by the XFS speculative preallocation ( https://linux-xfs.oss.sgi.narkive.com/jjjfnyI1/faq-xfs-speculative-preallocation ) Regards, Xavi On Sat, Feb 5, 2022 at 10:19 AM Strahil Nikolov wrote: > It seems quite odd. > I'm adding the devel list,as it looks