[LUDOC-313] Questions about setting up quota Created: 26/Nov/15  Updated: 14/Dec/15  Resolved: 14/Dec/15

Status: Closed
Project: Lustre Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: John Fuchs-Chesney (Inactive) Assignee: Richard Henwood (Inactive)
Resolution: Fixed Votes: 0
Labels: quota

Rank (Obsolete): 9223372036854775807

 Description   

Customer provided the following feedback, concerning the information provided in the current Lustre Operating Manual about how to set up quotas:

"My questions had to do with several issues.
(1) The manual lays out different approaches based on whether or not your lustre version is 2.4 or higher, but doesn’t explain how to verify what lustre version you’re using.
(2). The manual doesn’t make clear what server you’re supposed to run the various commands on. The section on enabling disk quotas, mentions the MGS server earlier in the section, but not lower down where it instructs you to issue the commands “lctl con_param testfs1.quota.ost=ug, and lcdl con_param testfs2.quota.mdt=g” I assumed this needed to be done on the MGS, and that seemed to work.
(3) At the end of the section on enabling disk quotas, the manual suggests you issue the command “lcdl get_param osd-..quota_slave.info”. I did this before enabling quotas to verify they were off, and it worked. I tried it again, on the MGS server, after enabling quotas, and got nothing but an error.
(4) In the section on Quota Administration, the manual makes no mention whatsoever of what server these commands should be run on. It took some thought and experimenting on my part to discover they need to be run from a lustre client, not a lustre server (correct me if I’m wrong).
At this point, I THINK the quotas are enabled and working properly, but I’m worried that the command I mention in (3) above is returning an error."



 Comments   
Comment by Gerrit Updater [ 30/Nov/15 ]

Richard Henwood (richard.henwood@intel.com) uploaded a new patch: http://review.whamcloud.com/17399
Subject: LUDOC-313 cleanup: Remove ambiguity in quota documentation.
Project: doc/manual
Branch: master
Current Patch Set: 1
Commit: 5cb7f977a1b5be3f9bd3367be54b7adb787986ae

Comment by John Fuchs-Chesney (Inactive) [ 08/Dec/15 ]

Feedback to Richard.

Q 1: is addressed.

Q 2: Customer is looking for explicit guidance as to which server to use for the following commands. " I assumed this needed to be done on the MGS, and that seemed to work." May be worth bolding or underlining this: " all setup commands in this section must be run on the MGS." to make it more distinctive.

Or repeat this guidance in the examples: "Examples:
To turn on user and group quotas for block only on file system testfs1, run:$ lctl conf_param testfs1.quota.ost=ug on the MGS server (assuming this is the correct guidance). Same with the other examples.

Q 3: I could not locate this text " “lcdl get_param osd-..quota_slave.info”." – so not able to see the improvement.

Q 4: If this "This is controlled entirely from a client via three quota parameters" is blanket guidance for the whole section I think it would be useful to highlight in some way.

Thanks Richard.

Comment by Richard Henwood (Inactive) [ 09/Dec/15 ]

Q2, done.

Q3: it is contained in section: 21.2.2.1. This command must be run on the MDS(s) - I've emphasized this.

Q4: done.

Version with these changes is here:
https://build.hpdd.intel.com/job/lustre-manual-reviews/618/artifact/lustre_manual.xhtml#configuringquotas

Comment by Gerrit Updater [ 14/Dec/15 ]

Richard Henwood (richard.henwood@intel.com) merged in patch http://review.whamcloud.com/17399/
Subject: LUDOC-313 cleanup: Remove ambiguity in quota documentation.
Project: doc/manual
Branch: master
Current Patch Set:
Commit: a591002608f4034150997adf079b7d93fa512c93

Generated at Sat Feb 10 03:41:56 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.