/proj/projname
), but the amount of data can be
stored is determined by the new project’s allocation.Long-term storage is available on other systems, e.g Swestore. ↩
There are two reasons to limit the number of files stored by a project. 1: certain operations, like checking/repairing the file system, and starting it after certain types of crashes, takes time proportional to the number of files in it. 2: every file, even empty ones, consumes a certain amount of storage space for metadata (filename, permissions, timestamps, …), which is not counted towards the normal quota. The files limit is currently not shown in NSC Express or SUPR. We will typically be generous when asked to raise this limit, it acts mostly as a tripwire to alert us to when a project starts storing data in a problematic way (millions of small files). ↩
Currently, we delete the data manually at some point 90 or more days after the project ends. If you notice that your data is missing but there’s more than 90 days since the project ended, please get in touch with NSC ASAP, if you are really lucky we have not yet deleted the data. ↩
Actually, the directory is not read-only, we set the quota to zero, which makes it impossible to write new data, but you can still delete data. You might call this “delete-only”. This makes it easier to move your data - you can delete files that have been moved and easily see what remains. ↩
Guides, documentation and FAQ.
Applying for projects and login accounts.