[Bugs] [Bug 1637196] Disperse volume 'df' usage is extremely incorrect after replace-brick.

[bugzilla at redhat.com]

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



--- Comment #2 from Jeff Byers <jbyers at stonefly.com> ---
The problem of the 'df' usage being wrong is because the
GlusterFS brick shared count 'shared-brick-count' for the
segments is being incremented, where it should have been
always been 1. What the 'shared-brick-count' is for is when a
volume has multiple bricks on the same file-system. In such
cases, as multiple bricks cannot use the full space of the
file-system since they are sharing, the space for only one of
them is counted.

However, in this case there was no brick file-system sharing
going on. GlusterFS uses the file-system ID from f_fsid field
from statvfs() to determine when multiple bricks are on the
same file-system.

Unfortunately, 'replace-brick' was not reading the
sys_statvfs() 'f_fsid' value from the new brick, so 'brick-
fsid' in the brick spec file was being set to 0. For the first
'replace-brick' this would be OK, but when another brick was
replaced, also with 'brick-fsid' being 0, there could then be
multiple bricks with the 'statfs_fsid' value of zero, so
'shared-brick-count' would be incremented, and its space would
be subtracted from the volume.

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