[Bugs] [Bug 1744950] glusterfs wrong size with total sum of brick.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1744950

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
          Component|core                        |glusterd



--- Comment #11 from Nithya Balachandran <nbalacha at redhat.com> ---
Does this volume have the same problem as the other one? If yes, the problem is
with the volfiles for the bricks on 10.10.2.22:

./vol_320b6dab471a7b810d92ff03e9ef05c6.10.51.2.22.var-lib-heketi-mounts-vg_d42ee5516f065e5f10b223bbb0a00d9b-brick_6078cfee3d8e48b50586b539fdfe8d61-brick.vol:
   option shared-brick-count 2

./vol_320b6dab471a7b810d92ff03e9ef05c6.10.51.2.22.var-lib-heketi-mounts-vg_19d11e2d0689d918b6affd2acfb2bcfe-brick_ebb2523fa96dbfe301c74e16428b04a0-brick.vol:
   option shared-brick-count 2


Both these have a shared-brick-count value of 2 which causes gluster to
internally halve the available disk size for these bricks. As they are on
different replica sets and the lowest disk space value of of the bricks is
taken for the disk space of the replica set, this means the value of the disk
space is halved for the entire volume.



This is the same problem reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1517260.


To recover, please do the following:

1. Restart glusterd on each node
2. For each volume, run the following command from any one gluster node:

gluster v set <volname> cluster.min-free-disk 11%


This should regenerate the volfiles with the correct values. Recheck the
shared-brick-count values after doing these steps - the values should be 0 or
1. The df values should also be correct.

Moving this to the glusterd component.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.