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.
Filesystems from those platforms are not cross-mounted either. This means that if you need to use data from another ECMWF platform such as ECGATE or the Cray HPCF, you will need to so transfer it first using scp or rsync. See Linux Virtual Desktop VDI: File transfers for more information.
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 | 20GB |
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 |
OneDrive | ||||
Environment variables
Those filesystems can be conveniently referenced from your session and scripts using the environment variables of the same name: $HOME, $PERM.
How much have I used?
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:
Before | After |
---|---|
/home/group/user or /home/ms/group/user | /home/user |
/perm/group/user or /perm/ms/group/user | /perm/user |
- | /hpcperm/user |
/scratch/group/user or /scratch/ms/group/user | /scratch/user |