Quota: Difference between revisions
No edit summary |
|||
| Line 13: | Line 13: | ||
Alternatively we now have some file systems that support RPC quotad quotas. These are reported to the user by the '''<tt>quota</tt>''' command. Home directories that are mounted from our Dell FluidFS NAS will support these kinds of quotas (/cliphomes, /cfarhomes, /cbcbhomes). | Alternatively we now have some file systems that support RPC quotad quotas. These are reported to the user by the '''<tt>quota</tt>''' command. Home directories that are mounted from our Dell FluidFS NAS will support these kinds of quotas (/cliphomes, /cfarhomes, /cbcbhomes). | ||
To find out what your current quota | To find out what your current quota is, first run '''<tt>df .</tt>''' to find out what file system you are currently mounted from (in this example it is <tt>fluidfs:/rama_cfarhomes/derek</tt>). '''Please note that the Use% here is for the entire file system and not just your home directory.''' | ||
<pre> | <pre> | ||
# df . | # df . | ||
| Line 21: | Line 21: | ||
</pre> | </pre> | ||
Then run '''<tt>quota</tt>''' and that line will list your quota information for that file system. If you see errors such as "Error while getting quota from ..." you may safely ignore these as some of our file systems such as Gluster do not report quotas correctly. | |||
<pre> | <pre> | ||
| Line 31: | Line 31: | ||
</pre> | </pre> | ||
If you have hit your RPC | If you have hit your RPC quota and haven't realized it, you may see some strange issues. For example, you will not be able to write-out files (although 'touch' and file concatenation will succeed). Some applications such as vi will throw "FSync" errors. Similarly, commands such as wget will appear to succeed but your files will be zero-length. | ||
Revision as of 16:54, 24 September 2018
Tree Quotas
The current most prevalent style of quota management is done through tree quotas that show up in how much space is available in the file system by using the df command to inspect either the current path (no arguments given) or a given path. NFShomes and many other file systems utilize this style of quota management.
For example to show my /nfshomes/derektest home directory quota i can just use df ~
$ df ~
Filesystem 1K-blocks Used Available Use% Mounted on
umiacsfs02:/nfshomes/derektest
1024000 49984 974016 5% /nfshomes/derektest
RPC Quotas
Alternatively we now have some file systems that support RPC quotad quotas. These are reported to the user by the quota command. Home directories that are mounted from our Dell FluidFS NAS will support these kinds of quotas (/cliphomes, /cfarhomes, /cbcbhomes).
To find out what your current quota is, first run df . to find out what file system you are currently mounted from (in this example it is fluidfs:/rama_cfarhomes/derek). Please note that the Use% here is for the entire file system and not just your home directory.
# df .
Filesystem 1K-blocks Used Available Use% Mounted on
fluidfs:/rama_cfarhomes/derek
1073741824 759351008 314390816 71% /cfarhomes/derek
Then run quota and that line will list your quota information for that file system. If you see errors such as "Error while getting quota from ..." you may safely ignore these as some of our file systems such as Gluster do not report quotas correctly.
$ quota
Disk quotas for user derek (uid 2174):
Filesystem blocks quota limit grace files quota limit grace
fluidfs:/rama_cfarhomes/derek
337560 0 10240000 0 0 0
If you have hit your RPC quota and haven't realized it, you may see some strange issues. For example, you will not be able to write-out files (although 'touch' and file concatenation will succeed). Some applications such as vi will throw "FSync" errors. Similarly, commands such as wget will appear to succeed but your files will be zero-length.