Bug 1256710 - [quota] Volume reset with force is not resetting the Quota daemon.
Summary: [quota] Volume reset with force is not resetting the Quota daemon.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Byreddy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-25 10:10 UTC by Byreddy
Modified: 2015-09-03 06:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-25 10:21:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Byreddy 2015-08-25 10:10:40 UTC
Description of problem:
To reset all the daemons running if we use "volume reset" with *force* option, it's resetting all the daemons except Quota daemon.


Version-Release number of selected component (if applicable):
**glusterfs-server-3.7.1-12**

How reproducible:
Always

Steps to Reproduce:
1.Create a Distributed volume.
2.Start the Volume  
3.Enable the Bitrot, Scrub, uss and Quota things.
4.Reset the volume using force (gluster volume reset <vol_name> force)
5.Check the Volume status (gluster volume status <vol_name>

Actual results:
Quota daemon is still running even after force volume reset.


Expected results:
Force volume reset should stop all the running daemons.

Additional info:

Comment 3 Vijaikumar Mallikarjuna 2015-08-25 10:21:09 UTC
Below operation are deprecated
   1) Enabling quota with volume set option
   2) Disabling quota with volume reset operation

However you can set/reset quota-deem-statfs option with volume set options.

When doing a volume reset operation on a volume where quota is enabled, this operation will turn 'ON' quota-deem-statfs


To enable/disable quota use below commands
gluster volume quota <volname> enable
gluster volume quota <volname> disable

Comment 4 SATHEESARAN 2015-09-03 03:49:23 UTC
(In reply to Vijaikumar Mallikarjuna from comment #3)
> Below operation are deprecated
>    1) Enabling quota with volume set option
>    2) Disabling quota with volume reset operation
> 
> However you can set/reset quota-deem-statfs option with volume set options.
> 
> When doing a volume reset operation on a volume where quota is enabled, this
> operation will turn 'ON' quota-deem-statfs
> 
> 
> To enable/disable quota use below commands
> gluster volume quota <volname> enable
> gluster volume quota <volname> disable

I have 2 concerns here :

1. When we say that disabling/enabling quota using volume set is deprecated, volume set should throw error, while the user tries to enable/disable quota through volume set/reset

2. Was it documented ?

Comment 5 Vijaikumar Mallikarjuna 2015-09-03 06:03:03 UTC
> (SATHEESARAN 2015-09-02 23:49:23 EDT comment #4)
> I have 2 concerns here :
>
>1. When we say that disabling/enabling quota using volume set is deprecated, volume set should throw error, while the user tries to enable/disable quota through volume set/reset
>
>2. Was it documented ?


Volume set/reset will throws error for quota options

# gluster volume set vol1 features.quota on
volume set: failed:  'gluster volume set <VOLNAME> features.quota on' is deprecated. Use 'gluster volume quota <VOLNAME> enable' instead.

# gluster volume reset vol1 features.quota
volume reset: failed: 'gluster volume reset <VOLNAME> features.quota' is deprecated. Use 'gluster volume quota <VOLNAME> disable' instead.

# gluster volume reset vol1 features.quota force
volume reset: failed: 'gluster volume reset <VOLNAME> features.quota' is deprecated. Use 'gluster volume quota <VOLNAME> disable' instead.


We will check with doc-team regarding the documentation.


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