| 2 | |
| 3 | On the DEEP-EST system, three different groups of filesystems are available: |
| 4 | - the |
| 5 | [http://www.fz-juelich.de/ias/jsc/EN/Expertise/Datamanagement/OnlineStorage/JUST/Filesystems/JUST_filesystems_node.html JSC GPFS filesystems], |
| 6 | provided via [http://www.fz-juelich.de/ias/jsc/EN/Expertise/Datamanagement/OnlineStorage/JUST/JUST_node.html JUST] and mounted on all JSC systems; |
| 7 | |
| 8 | - the DEEP-EST parallel BeeGFS filesystems, available on all the nodes of the DEEP-EST system; |
| 9 | |
| 10 | - the filesystems local to each node. |
| 11 | |
| 12 | The users home folders are placed on the shared GPFS filesystems. With the advent of the new user |
| 13 | model at JSC |
| 14 | ([http://www.fz-juelich.de/ias/jsc/EN/Expertise/Supercomputers/NewUsageModel/NewUsageModel_node.html JUMO]), the shared filesystems are structured as follows: |
| 15 | - $HOME: each JSC user has a folder under `/p/home/jusers/`, in which different |
| 16 | home folders are available, one per system he/she has access to. These home |
| 17 | folders have a low space quota and are reserved for configuration files, ssh |
| 18 | keys, etc. |
| 19 | |
| 20 | - $PROJECT: In JUMO, data and computational resources are assigned to projects: |
| 21 | users can request access to a project and use the resources associated to it. |
| 22 | As a consequence, each user has a folder within each of the projects he/she is part |
| 23 | of. For the DEEP project, such folder is located under `/p/project/cdeep/`. |
| 24 | Here is where the user should place data, and where the old files generated |
| 25 | in the home folder before the JUMO transition can be found. |
| 26 | |
| 27 | The DEEP-EST system doesn't mount the $SCRATCH and $ARCHIVE filesystems, as it is |
| 28 | expected to provide similar functionalities with its own parallel filesystems. |
| 29 | |