The file systems managed in this way are short, home and the mdss file storage area. The concept of a "quota" and "hard" limit is used. The "quota" limits should be seen as the real limits users must try to stay under, while the hard limit is used by the system as a trigger to take immediate action.
A user or project which exceeds the quota limits but not the hard limits has seven days in which to get back under quota to avoid the actions triggered by the hard limit exceptiom.
The consequences of a project or user exceeding these limits on the short, mdss or home areas are outlined in the table below.
Users should ensure they have enough space available before starting jobs. Note that adjustments to quotas, on a temporary or a long-term basis, will be made given reasonable justification.
| File System | Quota Limit Exceeded | Hard Limit Exceeded |
|---|---|---|
| short | All members of the project will be sent an email to inform them that the project has exceeded the quota limit, and that they must reduce the disk space used under short within 7 days to avoid access to the batch queues being removed for the project. | Access to the queues by the project will be placed on
hold until the disk usage is reduced by the project. All
members of the project will be sent an email to inform them of
this fact. Queued jobs will be released and access to the queues will be reactivated when the cron job next runs and detects that the disk usage is back under the quota limit. This should occur within 5 minutes of the project getting back under the disk quota limit. |
| mdss | All members of the project will be sent an email to inform them that the project has exceeded the quota limit, and that they must reduce the file space used on the MDSS system within 7 days to avoid access to the batch queues being removed for the project. | Access to the queues by the project will be placed on
hold until the file space usage is reduced by the project. All
members of the project will be sent an email to inform them of
this fact.
Due to the relative "expense" of reassessing file space usage under mdss, reactivation will not automatically occur for up to 3 hours after the removal of files. Contact to request manual reactivation. |
| home | The user will be sent an email to warn them that their disk usage under home is over the quota limit and they must reduce the disk space used within 7 days to avoid access to the batch queues being removed for the user. | Access to the queues for the user will be placed on hold until
their home disk usage is reduced below the limit. An email
will be sent to inform the user of this fact. Queued jobs will be restarted and access to the queues will be reactivated when the cron job next runs and detects that the disk usage is back under the limit. This should occur within 5 minutes of the user getting back under the disk quota limit. |