Bug 1566823

Summary: fuse: synthetic stavfs values are confusing
Product: [Community] GlusterFS Reporter: Csaba Henk <csaba>
Component: fuseAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-13 04:37:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Csaba Henk 2018-04-13 04:29:29 UTC
Description of problem:

Instead of passing over the respective values obtained from backend, fuse xlator specifies stavfs values (in particular, f_{b,fr}size) on its own.

This is confusing as the size granularity, and therefore the fs sizes reported by df and similar tools will differ within different protocols.

See http://lists.gluster.org/pipermail/gluster-devel/2018-March/054660.html for more background on the phenomenon.

Comment 1 Csaba Henk 2018-04-13 04:37:14 UTC

*** This bug has been marked as a duplicate of bug 1523219 ***