On a gluster volume with 100GB if we try to create a gluster-block of size 100GB with pre-allocation, block creation succeeds but it silently fails to allocate the correct sizes for the shards on the posix xlator.
sh-4.2# du -sh .shard/* | awk '{print $1}' | sort | uniq -c
1 18M
1 26M
1597 64M
Because of this when writes happen on a pre-allocated block device, writes fail with ENOSPC which shouldn't happen for preallocated files.
COMMIT: https://review.gluster.org/20269 committed in release-4.1 by "Pranith Kumar Karampuri" <pkarampu> with a commit message- storage/posix: Handle ENOSPC correctly in zero_fill
Change-Id: Icc521d86cc510f88b67d334b346095713899087a
fixes: bz#1591185
Signed-off-by: Pranith Kumar K <pkarampu>
(cherry picked from commit 6ef91480f9e75f63100585bfd19694deb0c2457b)
On a gluster volume with 100GB if we try to create a gluster-block of size 100GB with pre-allocation, block creation succeeds but it silently fails to allocate the correct sizes for the shards on the posix xlator. sh-4.2# du -sh .shard/* | awk '{print $1}' | sort | uniq -c 1 18M 1 26M 1597 64M Because of this when writes happen on a pre-allocated block device, writes fail with ENOSPC which shouldn't happen for preallocated files.