Bug 1029955 - Quota: quota-remove-xattr.sh should not be executed when you disable quota on a volume where quota is already disabled.
Summary: Quota: quota-remove-xattr.sh should not be executed when you disable quota on...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: quota
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact: Saurabh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-13 15:32 UTC by Gowrishankar Rajaiyan
Modified: 2016-09-17 12:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-06 09:40:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Gowrishankar Rajaiyan 2013-11-13 15:32:32 UTC 
Description of problem: Disabling quota when it is already disabled triggers quota-remove-xattr.sh.


Version-Release number of selected component (if applicable):
glusterfs-3.4.0.44rhs-1.el6rhs.x86_64


How reproducible: Always


Steps to Reproduce:
1. Diable quota on a volume.
2. Ensure that quota-remove-xattr.sh has finished. (from the output of ps)
3. Disable quota again.

Actual results: quota-remove-xattr.sh is triggered again.


Expected results: Disabling quota when it is already disabled should not trigger quota-remove-xattr.sh.


Additional info:
Comment 2 Vijaikumar Mallikarjuna 2015-07-30 09:46:25 UTC 
This is not happening in glusterfs-3.7.1. Please verify
Comment 3 Vijaikumar Mallikarjuna 2015-08-06 09:40:02 UTC 
Not seeing this issue with glusterfs-3.7.1. Please file a new bug if the issue is seen again in the latest build
Note You need to log in before you can comment on or make changes to this bug.