Versions Compared

Old Version 14

changes.mady.by.user Diego Molinari

Saved on

compared with

New Version 15

changes.mady.by.user Diego Molinari

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You are strongly encouraged to use these environment variables instead of full paths to refer to data in your scripts and codes.

Summary

$CINECA_SCRATCH$WORK$DRES

Created when username has granted access.
Each username has its own area (and only one).

Created when a project is opened.
Each project has its own area.
All collaborators can write.
Each user has as many $WORK areas as active projects.

Created on request.
Not connected to a specific project.
Data are accessible by all the platforms but visible only to login nodes and nodes of the serial partition. Compute nodes do not see $DRES area.

A clean-up procedure is active.
Files older then 40 days are cancelled daily.
No backup

Data are preserved up to few months after the end of the project.
No backup.

Data are preserved up few months after the expiring date
No backup.
No quota.Default quota of 1 TB. Motivated requests for quota increase will be taken into account.

Quota based on the needs.
A limit of 2000 files each TB is present.

By default files are public (read only). The user can change the permission (chmod) and make files private. It is not possible to restrict access to the group (all username share the same mail unix group).By default files are private. The user can change the permission (chmod) and make files visible (R o R/W) to project collaborators.Same as $WORK area.

What to use when...

Data are critical, not so large, I want to be sure to preserve them.$HOME is the right place. Pay attention to the 50 GB quota limit for each user on this space.
Large data to be shared with collaborators of my project.$WORK is the right place. Here each collaborator can have his own directory. He can open it for reading or even writing and be sure, at the same time, that data are not public. People not included in the project will not be able to access the data. Moreover data are preserved up to few months after the project’s end.
Data to be shared with other users, not necessarily participating to common projects

$CINECA_SCRATCH is the right place.

Data to be maintained even beyond the end of the project. I'll use the data on different CINECA hosts$DRES is the better solution.
Data to be shared among different platforms$DRES allows this.

Monitoring the occupancy

A command is available on all HPC systems to check the status of the occupancy of all the area accessible by the user and eventually the presence of a quota limit.

...

If you are a DRES user, output of cindata command will contain similar lines:

UI Text Box

USER       AREADESCR                        AREAID                       FRESH    USER           AREADESCR                        AREAID                  FRESH    USED      QTA    USED%    aUSED   aQTA   aUSED%

myuser00  /gpfs/work/<AccountName>       galileo_work-Acc-name          9hou     114G      --      --%      14T      30T    48.8%

myuser00  /gpfs/scratch/                 galileo_scr                    9hou     149G      --      --%     341T     420T    81.2%

myuser00  /galileo/home                  galileo_hpc-home               9hou     5.7G      50G     11.4%    16T       --      --%

myuser00  /gss/gss_work/DRES_myAcc       work_OFFLINE-DRES_myAcc-FS     9hou     2.9G      --      --%      11T      15T    73.3%

myuser00  /gss/gss_work/DRES_myAcc       work_ONLINE-DRES_myAcc-FS      9hou     1.2T      --      --%     2.8T       4T    70.0%

...