Hi!
I opened a Github issue https://github.com/gluster/glusterfs/issues/3206
but not sure how much attention they get there, so re-posting here just in
case someone has any ideas.
Description of problem:
GlusterFS 9.5, 3-node cluster (2 bricks + arbiter), an attempt to tar the
whole filesystem
I tried setting the shard size to 512MB. It slightly improved the space
utilization during creation - not quite double space utilization. And I
didn't run out of space creating a file that occupied 6gb of the 8gb volume
(and I even tried 7168MB just fine). See attached command line log.
On Fri,
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
well, I tried to downgrade to 8.6 on node gluster07. It didn't help.
Fortunately I remember old post from Strahil in ovirt list which
suggests to switch
gluster volume set cluster.lookup-optimize off
when expanding cluster. As nodes were rejected due cksum mismatch on
only one volume I
Hello,
I have a glusterfs cluster in version 8.6, 6 nodes, 1 arbiter node,
distributed-replicated setup with arbiter (Number of Bricks: 3 x (2 + 1)
= 9).
Yesterday I added two new nodes. Because I plan to upgrade to gluster 9
I have installed them with Rocky Linux 8 and glusterfs 9 (from
