Workspaces/Advanced Features/Quotas
Jump to navigation
Jump to search
Cluster-Specific Workspace Limits
Different clusters have different workspace policies configured in /etc/ws.conf. Below is an overview of typical settings:
| Cluster | Default Lifetime | Max Lifetime | Max Extensions | User Quota | Inode Quota |
|---|---|---|---|---|---|
| bwUniCluster 3.0 | 1 day | 60 days | 3 times | 40 TiB | 20 million |
| JUSTUS 2 | 7 days | 90 days | Unlimited | 20 TiB | 5 million |
| Helix | N/A | 30 days | 10 times | 10 TiB | None |
| BinAC2 | N/A | 30 days | 5 times | None | None |
| NEMO2 | 30 days | 100 days | 100 times | 5 TiB per workspace | None |
Configuration Parameters
Configuration parameters in /etc/ws.conf:
- duration - Maximum lifetime in days
- maxextensions - Number of times a workspace can be extended
- keeptime - Days to keep expired workspaces before final deletion (typically 7-30 days)
- Released workspaces have a shorter grace period (~1 hour) regardless of keeptime
Note: Check your specific cluster documentation for current quotas and settings, as they may change. Use ws_list -l to see available filesystems and their properties on your cluster.
Checking Workspace Quotas
The command to check workspace quota usage varies by cluster and filesystem:
Lustre-based clusters
bwUniCluster 3.0, JUSTUS 2:
$ lfs quota -uh $(whoami) /lustre/work # or appropriate workspace path $ lfs quota -uh $(whoami) /pfs/work9 # bwUniCluster 3.0
NEMO2 (Weka filesystem)
$ nemoquota # Shows HOME and workspace quotas $ df --si $(ws_find workspace_name) # Check specific workspace
Helix (IBM Spectrum Scale)
$ workquotainfo # Shows workspace quota info
BinAC2
- No quota limits enforced on workspaces
- Check available space with df command
General tip
Always check disk usage before large data operations to ensure sufficient space is available.
For quota management strategies, see Immediate Deletion methods.