Bug 1398381

Summary: Hole punch does not report correct size
Product: [Community] GlusterFS Reporter: Ram Ankireddypalle <areddy>
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED EOL QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.7.8CC: amukherj, bugs, rhs-bugs, sasundar, storage-qa-internal
Target Milestone: ---Keywords: Triaged
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: 2016-12-02 06:41:08 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 Ram Ankireddypalle 2016-11-24 15:51:29 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.On a normal XFS file system:
==============================
0:root@vm4 ~$ #create a file.
0:root@vm4 ~$ echo > file
0:root@vm4 ~$ #fallocate 1G with keep size flag.
0:root@vm4 ~$ fallocate -o0 -l1G -n file
0:root@vm4 ~$ #check file size and disk space usage.
0:root@vm4 ~$ ll -h file
-rw-r--r--. 1 root root 1 Nov 11 22:09 file
0:root@vm4 ~$ du -h file
1.0G    file


On a normal plain distribute 1 brick volume using fuse mount:
===============================================================
0:root@vm4 fuse_mnt$ echo >file
0:root@vm4 fuse_mnt$ fallocate -o0 -l1G -n file
0:root@vm4 fuse_mnt$ ll -h file
-rw-r--r--. 1 root root 1 Nov 11 22:13 file
0:root@vm4 fuse_mnt$ du -h file
512     file -->This is wrong.
2.
3.

Actual results:
The file size is being reported as 512 on gluster mount point.

Expected results:
The file size should be reported as 1G on gluster mount point.

Additional info:
Comment 2 hari gowtham 2016-12-02 06:41:08 UTC 
This bug is getting closed because the 3.6 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.