In virtualization sharding is quite common (yet, on replica volumes) and I have never observed such behavior.
Can you increase the shard size to 512M and check if the situation is better ?
Also, share the volume info.
Best Regards,
Strahil Nikolov
On Fri, Feb 4, 2022 at 22:32, Fox<foxxz.net@xxxxxxxxx> wrote:________Using gluster v10.1 and creating a Distributed-Dispersed volume with sharding enabled.I create a 2gb file on the volume using the 'dd' tool. The file size shows 2gb with 'ls'. However, 'df' shows 4gb of space utilized on the volume. After several minutes the volume utilization drops to the 2gb I would expect.This is repeatable for different large file sizes and different disperse/redundancy brick configurations.I've also encountered a situation, as configured above, where I utilize close to full disk capacity and am momentarily unable to delete the file.I have attached a command line log of an example of above using a set of test VMs setup in a glusterfs cluster.Is this initial 2x space utilization anticipated behavior for sharding?It would mean that I can never create a file bigger than half my volume size as I get an I/O error with no space left on disk.
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-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
________ 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-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
