Storage limits and responsibilities
This page states only what is currently established. Where something could not be confirmed, that is said plainly rather than guessed.
What is confirmed#
| Location | Limit | Evidence |
|---|---|---|
/home/<KU-ID> | 100 GB, enforced | Live-verified |
/projects/<project>/ | No quota mechanism found | Live-verified — quota reports no quota enabled on project storage |
The project filesystem's large total capacity (petabyte scale) is a shared filesystem capacity, not a per-project allocation — it says nothing about how much any one project is entitled to use. Do not read a large df total as your quota.
Note The absence of an enforced project quota is not an invitation to store without limit. Project storage is a shared, finite, costed resource used by many groups — see below.
Checking your own usage#
There is no quota to check, but you can measure what you're actually using:
du -sh /projects/<project>/people/<KU-ID>/This can take a while on a large directory. For a quick per-subfolder breakdown:
du -sh /projects/<project>/people/<KU-ID>/*What could not be established as current#
Storage costs. Historical announcements from 2025 discussed storage charging and a possible per-project allowance, and a later 2025 announcement described that cost model as still preliminary at the time. Current pricing and allocation were not established during this review, and no historical figure is repeated here — a stale number would be worse than no number.
scratch (see Where should my files go?) is temporary working storage and is not backed up. Because it lacks backup protection, it is usually priced lower than backed-up storage — but that is not necessarily the only factor in UCPH's pricing, and no fixed price relationship is guaranteed. For current storage pricing, check KUnet; no price is repeated here for the same reason as above.
If storage cost matters for your planning or budgeting more generally, ask through Getting help for the current position.
Storage usage reporting. The same historical announcements described monthly emailed usage reports to users and PIs. Whether that reporting is currently active could not be established from available evidence. If you need a usage report, ask.
Institutional responsibility#
Mjolnir does not have its own separate storage or data-protection policy. Responsibility for research data — retention, protection, and institutional requirements — sits with University of Copenhagen policy, not with this Knowledge Base:
- UCPH Policy for Research Data Management — the university's formal policy, including data management plans and the FAIR principles
- Research data support (KU Library) — practical help preparing a data management plan
- UCPH Research and Information Security — for sensitive or personal data questions
For what Mjolnir itself can tell you — where something lives, whether it can be recovered, and what to do about a full project directory — use Getting help.