Bug 1336304 - [quota]: Observing quota usage be 100% with no data in the volume
Summary: [quota]: Observing quota usage be 100% with no data in the volume
Keywords:
Status: CLOSED DUPLICATE of bug 1196026
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: quota
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Manikandan
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-16 06:57 UTC by Rahul Hinduja
Modified: 2016-09-20 04:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 05:26:24 UTC
Embargoed:


Attachments (Terms of Use)

Description Rahul Hinduja 2016-05-16 06:57:52 UTC
Description of problem:
=======================

While running georep cases, found an issue where the volume shows 100% used while in actual, no data is present in the volume. Quota is enabled on volume and limit is set to 100G.

disk free on quota shows 0 Avail

[root@dhcp37-182 ~]# df -h /run/gluster/master
Filesystem        Size  Used Avail Use% Mounted on
localhost:master  100G  100G     0 100% /run/gluster/master
[root@dhcp37-182 ~]# 

Quota list shows used as PB 

[root@dhcp37-182 ~]# gluster volume quota master list 
                  Path                   Hard-limit  Soft-limit      Used  Available  Soft-limit exceeded? Hard-limit exceeded?
-------------------------------------------------------------------------------------------------------------------------------
/                                        100.0GB     80%(80.0GB) 16384.0PB 100.0GB              No                   No
[root@dhcp37-182 ~]# 



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

glusterfs-3.7.9-4.el7rhgs.x86_64


How reproducible:
=================
1/1, will have to retry to confirm the number of occurrence.

Steps Carried:
==============

These Steps are from geo-replication test case point of view which were carried. 
1. Create Master/Slave cluster and Volume
2. Enable Quota On Master and Slave
3. Create georep session between master/slave volume
4. Create Data (200M) and Let it sync to slave
5. Remove from Master (rm -rf *)
6. At this point no data present at master and slave.

Actual results:
===============

quota list showing wrong values in list

Comment 2 Manikandan 2016-06-13 05:56:36 UTC
Hi Rahul,

The issue is reproducible on a normal volume itself when doing a rm -rf from mount point. There are some fixes relating to rm issue which will be part of 3.1.3. Could you please test the same on the master branch or on 3.1.3 and let us know if the issue is still seen?

--
Thanks & regards,
Manikandan Selvaganesh.

Comment 3 Manikandan 2016-06-29 05:26:24 UTC

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


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