cluster:100
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cluster:100 [2011/03/27 21:21] hmeij |
cluster:100 [2011/03/28 14:23] (current) hmeij |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ==== Quotas ==== | ==== Quotas ==== | ||
| + | |||
| + | On 03/25/2011 quotas have been enabled on cluster greentail. | ||
| + | |||
| + | Here is what was put in place, and will mature/ | ||
| + | |||
| + | * A quota is not disk space allocated for you, as in reserved. | ||
| + | * Reason for quotas: to avoid /home from filling up by a runaway process, and constrain large users from growing beyond arbitrary thresholds. | ||
| + | |||
| + | The quotas fall into two tiers: the " | ||
| + | |||
| + | * In the sliding tier, when you reach your soft limit, notify HPC admins and your quota will slide to the next strata (< 90/100G, < 225/250G, < 450/500G). Once you exceed the last strata, and you still need more disk space, you enter the custom tier. | ||
| + | * In the custom tier, we discuss setting a quota after agreeing on size and availability of disk space, plus 100G. Then you are on your own. (Users that currently fall into this group have been grandfathered in and notified). | ||
| + | |||
| + | We urge all users to consider archiving data and files off the cluster disk array. | ||
| + | |||
| + | How to find my quota? You can find your quota levels and current usage as follows. | ||
| + | |||
| + | * The hard block limit is the absolute maximum amount of disk space that a user can use. Once this limit is reached, no additional disk space can be used. Writes to disks will fail. | ||
| + | * The soft block limit defines the maximum amount of disk space that can be used. Unlike the hard limit, the soft limit can be exceeded for a certain amount of time. That time is known as the grace period. Warnings will appear in your terminal/ | ||
| + | * The grace period is globally set for 7 days. | ||
| + | * We do not enforce inode limits. | ||
| + | |||
| + | < | ||
| + | |||
| + | [hmeij@greentail ~]$ quota -v hmeij | ||
| + | |||
| + | Disk quotas for user hmeij (uid 8216): | ||
| + | | ||
| + | / | ||
| + | 1227284 | ||
| + | |||
| + | </ | ||
| + | |||
| ==== Notes ==== | ==== Notes ==== | ||
| - | | + | **Implementation** |
| * add usrquota, | * add usrquota, | ||
| * log everybody out or reboot (quota error on boot, not initialized yet) | * log everybody out or reboot (quota error on boot, not initialized yet) | ||
| Line 17: | Line 51: | ||
| * group quota numbers do not add up !? | * group quota numbers do not add up !? | ||
| - | | + | **Array** |
| - | * 48 TB minus 4 global spares | + | |
| - | * after formatting 36 TB available | + | * 48 one TB disk minus 4 global spares |
| - | * /home 10, / | + | * after formatting 36 TB available |
| + | * /home 12 disks, / | ||
| + | * leaves | ||
| * snapshots holds base plus deltas hence needs to be somewhere between 1-2x base | * snapshots holds base plus deltas hence needs to be somewhere between 1-2x base | ||
| - | * so if we wanted to increase home, we could not use sanscratch (is anybody using it?) | + | * so if we wanted to increase home, we delete |
| * if we do not backup, then ... questions for later | * if we do not backup, then ... questions for later | ||
| - | | + | **Links** |
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| - | * [[http:// | + | * [[http:// |
| \\ | \\ | ||
| **[[cluster: | **[[cluster: | ||
cluster/100.1301260903.txt.gz · Last modified: 2011/03/27 21:21 by hmeij
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
