[Bugs] [Bug 1523219] New: fuse xlator uses block size and fragment size 128KB leading to rounding off in df output

[bugzilla at redhat.com]

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

            Bug ID: 1523219
           Summary: fuse xlator uses block size and fragment size 128KB
                    leading to rounding off in df output
           Product: GlusterFS
           Version: mainline
         Component: fuse
          Assignee: bugs at gluster.org
          Reporter: rtalur at redhat.com
                CC: bugs at gluster.org



Description of problem:
This difference is because FUSE uses a block size and fragment size of 128K
instead of using the backend filesystem's block size.

When statvfs call is made, this is the statvfs buffer content

      blocks  bfree   bavail
gfapi 259584, 248433, 251028
brick 259584, 251028, 251028
fuse    8112,   7763,   7844


As you can see, gfapi and brick match in total blocks and bavail.
There is a difference in bfree because of posix xlator. Posix xlator deducts 1%
of the total blocks from free blocks.

The numbers in fuse are the numbers in gfapi row divided by 32(because the
numbers obtained from brick are for 4K blocks and fuse wants to communicate in
terms of 128K blocks). Here, we are converting into a larger unit and value is
rounded off.

df on a mount point would get data from fuse and hence the discrepancy.

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