Bug 1398381 - Hole punch does not report correct size
Summary: Hole punch does not report correct size
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: 3.7.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-24 15:51 UTC by Ram Ankireddypalle
Modified: 2016-12-02 14:06 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-02 06:41:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.