Bug 1339689 - RFE - capacity info (df -h on a mount) is incorrect for a tiered volume
Summary: RFE - capacity info (df -h on a mount) is incorrect for a tiered volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Dan Lambright
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1333220 1367842
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-25 15:37 UTC by Dan Lambright
Modified: 2017-03-27 18:19 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.9.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1333220
Environment:
Last Closed: 2017-03-27 18:19:04 UTC
Regression: ---
Mount Type: fuse
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Dan Lambright 2016-05-25 15:37:58 UTC
+++ This bug was initially created as a clone of Bug #1333220 +++

Description of problem:
With a teired volume, a df -h shows a capacity equal to the hot + cold tiers. This is wrong, since the hot tier is a cache layer not an extension of the volumes capacity.

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

How reproducible:


Steps to Reproduce:
1. create a tiered volume
2. mount it and run df -h 


Actual results:
df -h shows a combined capacity view of hot+cold

Expected results:
df -h should show the capacity of the cold tier, since the cache layer is 'transient'. 

Additional info:

Comment 1 Vijay Bellur 2016-05-25 17:54:59 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier: run statfs on cold tier) posted (#1) for review on master by Dan Lambright (dlambrig)

Comment 2 Vijay Bellur 2016-06-01 18:38:14 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier:  fix statfs for tiered volumes) posted (#2) for review on master by Dan Lambright (dlambrig)

Comment 3 Vijay Bellur 2016-06-07 14:14:41 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier:  fix statfs for tiered volumes) posted (#3) for review on master by Dan Lambright (dlambrig)

Comment 4 Vijay Bellur 2016-06-17 18:37:17 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier:  fix statfs for dht/tiered volumes) posted (#4) for review on master by Dan Lambright (dlambrig)

Comment 5 Vijay Bellur 2016-06-21 16:40:37 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier:  fix statfs for dht/tiered volumes) posted (#5) for review on master by Dan Lambright (dlambrig)

Comment 6 Vijay Bellur 2016-06-27 17:27:37 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier:  fix statfs for dht/tiered volumes) posted (#6) for review on master by Dan Lambright (dlambrig)

Comment 7 Vijay Bellur 2016-07-26 14:00:57 UTC
REVIEW: http://review.gluster.org/14536 (cluster/tier:  fix statfs for dht/tiered volumes) posted (#7) for review on master by Dan Lambright (dlambrig)

Comment 8 Vijay Bellur 2016-07-27 13:03:52 UTC
COMMIT: http://review.gluster.org/14536 committed in master by Dan Lambright (dlambrig) 
------
commit 64ae3907818ad3cdaed1a1454cb44f684c9fcffd
Author: Dan Lambright <dlambrig>
Date:   Wed May 25 13:54:13 2016 -0400

    cluster/tier:  fix statfs for dht/tiered volumes
    
    Return the correct size of the tiered volume in statfs. It should
    be the size of the cold tier, not the sum of the hot and cold tier,
    because the hot tier is a cache and not an extension of the volume's
    capacity. The number of free blocks, etc is the cold tier's capacity
    subtracted by the sum of utilization on the hot and cold tiers. Note
    if both tiers are part of the same file system this must be accounted
    for as well.
    
    The patch also fixes a pre-existing bug in the DHT/tier
    translators. If statfs was taken on a file, the code only calculated
    free space on the cached subvolume, not all subvolumes in the replica
    group. With the fix, this is corrected, except in the case
    where quota is used with the deem-statfs option set to "on".
    
    Change-Id: I2b8bcb4511edf83f12130960aad0a609fcf8f513
    BUG: 1339689
    Signed-off-by: Dan Lambright <dlambrig>
    Reviewed-on: http://review.gluster.org/14536
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 9 Shyamsundar 2017-03-27 18:19:04 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.

glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/


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