- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
Project filesystem: Difference between revisions
(sprachliche Korrekturen) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
In addition to the HOME file system, there is also a project file system available | In addition to the HOME file system, there is also a project file system available which is mounted on all platforms located in the HWW environment at HLRS. It serves the purpose that project members within the project can share smaller amounts of data such as applications, input data for simulations or configuration files with other project members. The projects do not automatically get access to this file system. Please request [http://www.hlrs.de/trouble-ticket-submission-form/ via ticket system] if you need a project directory, then we will set it up for you. | ||
This filesystem is located on a shared RAID system and | This filesystem is located on a shared RAID system and is mounted via NFS on all login (frontend) and compute nodes. | ||
The path to the projects directories is consistent across all nodes. The filesystem space on this filesystem is limited by a small quota (50GB per user, 200GB per group)! The quota usage for your account and your groups can be listed using the <tt>na_quota</tt> command on the login nodes. | The path to the projects directories is consistent across all nodes. The filesystem space on this filesystem is limited by a small quota (50GB per user, 200GB per group)! The quota usage for your account and your groups can be listed using the <tt>na_quota</tt> command on the login nodes. | ||
{{Warning|text=Due to the limited network performance, the project filesystem is not intended for use in | {{Warning|text=Due to the limited network performance, the project filesystem is not intended for use in massively parallel compute jobs! For large compute jobs please use the [[workspace mechanism]] which uses the [http://en.wikipedia.org/wiki/Lustre_%28file_system%29 Lustre] based scratch directories. }} | ||
== Details == | == Details == | ||
| Line 11: | Line 11: | ||
* Userquota limit on filesystem: 50GB | * Userquota limit on filesystem: 50GB | ||
* Groupquota limit on filesystem: 200GB | * Groupquota limit on filesystem: 200GB | ||
* | * information about quota usage: <tt>na_quota</tt> | ||
* | * Availability/Access: project directory will only be set up if there is an according request. It is only available during project lifespan. <font color=red>After the end of the project, access, all data, all subdirs will be removed immediately!</font> | ||
* Backup: NO | * Backup: NO | ||
Latest revision as of 12:29, 15 November 2023
In addition to the HOME file system, there is also a project file system available which is mounted on all platforms located in the HWW environment at HLRS. It serves the purpose that project members within the project can share smaller amounts of data such as applications, input data for simulations or configuration files with other project members. The projects do not automatically get access to this file system. Please request via ticket system if you need a project directory, then we will set it up for you.
This filesystem is located on a shared RAID system and is mounted via NFS on all login (frontend) and compute nodes. The path to the projects directories is consistent across all nodes. The filesystem space on this filesystem is limited by a small quota (50GB per user, 200GB per group)! The quota usage for your account and your groups can be listed using the na_quota command on the login nodes.
Details
- Projects path: /zhome/projects/groups/<groupname>
- Subdirs for each project: common, <username>
- Userquota limit on filesystem: 50GB
- Groupquota limit on filesystem: 200GB
- information about quota usage: na_quota
- Availability/Access: project directory will only be set up if there is an according request. It is only available during project lifespan. After the end of the project, access, all data, all subdirs will be removed immediately!
- Backup: NO