...
| group | ecmwf |
|---|
The filesystems available are
...
HOME and PERM
...
.
...
...
| group | ecmwf |
|---|
The filesystems available are HOME, PERM, and are completely isolated from those in other ECMWF platforms in Reading such as ECGATE or the Cray HPCF.
...
File |
|---|
...
File System | Suitable for ... | Technology | Features | Quota | ||
|---|---|---|---|---|---|---|
| HOME | permanent files, e. g. .profile, utilities, sources, libraries, etc. | NFS | It is backed up. Limited I/O performance | 20GBSee HPC2020: Filesystems | ||
| PERM | permanent files without the need for automated backups, smaller input files for serial or small processing, std output, etc. | NFS | It is backed up. Limited I/O performance | 20GB | OneDriveSee HPC2020: Filesystems | |
OneDrive | Sharing information with end user device and other ECMWF or external users | Microsoft | Cloud based. See How to configure and mount OneDrive - Linux Virtual Desktop VDI FAQ | 1TB (see OneDrive) | ||
| Warning |
|---|
Please be aware that any "local" filesystems, like /tmp, will be cleaned up every month when the virtual machine is recreated from the latest updated image. So do not use those to store any information that you may want to keep. |
| Tip | ||
|---|---|---|
| ||
Those filesystems can be conveniently referenced from your session and scripts using the environment variables of the same name: $HOME, $PERM, $HPCPERM, $SCRATCH, $SCRATCHDIR and $TMPDIR. $TEMP, which in the past was an alias to $SCRATCH, has been deprecated and is no longer defined. Please use $SCRATCH instead | ||
| Tip | ||
| ||
If the limits on the SSD-backed $TMPDIR on the shared nodes are not enough for you, you may point your TMPDIR to SCRATCHDIR: No Format | |
| Tip | ||
|---|---|---|
| ||
You can check your current usage and limits with the "ecquota" command |
New filesystem structure
You will notice your filesystems have now a flatter and simpler name structure. If you port any scripts or code that had paths to filesystems hardcoded from older platforms, please make sure you update them. Where possible, try and use the environment variables provided, which should work on both sides pointing to the right location in each case:
...