This filesystem is mounted on login nodes of all HPC clusters in Cineca. Files retention is related to the life of the username: data are preserved until the username remains active.

Environment variables

...

Backup policies

The $HOME filesystem is guaranteed by daily backups. In particular cases, a different agreement is possible: contact the HPC support (superc@cineca.it) for further details.

The backup procedure runs daily and we preserve a maximum of three different copies of the same file. Older versions are kept for 1 month. The last version of deleted files is kept for 2 months, then definitely removed from the backup archive.

Environment variables

$HOME, $WORK,$CINECA_SCRATCH and $DRES environment variables are defined on all HPC Systems, and you can access these areas simply using those names:

UI Text Box
cd $HOME cd $CINECA_SCRATCH cd $WORK cd $DRES

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

UI Text Box
cd $HOME cd $CINECA_SCRATCH cd $WORK cd $DRES

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.

...

UI Text Box

USER AREADESCR AREAID FRESH USED QTA USED% aUSED aQTA 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%

This may be tricky to interpret. OFFLINE area is the DRES data that has been stored on tape, after 3 months of storage (see DRES description above). ONLINE area is the DRES data still in FS or ARCH area. The total quota of storage capability assigned to your DRES is indicated in the "aQTA" parameter of the line "OFFLINE". When DRES is empty, the correspondent value of the line "ONLINE" will be the same as "OFFLINE", but when files begin to be moved it will decrease, while the "aUSED" parameter of OFFLINE will increase accordingly. It means that you have less space that you can use to store your data, since some of the already used space has been moved to tape. Similarly, deleting offline data will decrease the aUSED parameter in OFFLINE, and increase the aQTA parameter in ONLINE of the same amount. The formula to remember is:

TOTAL DRES STORAGE = aQTA-OFF = aQTA-ON + aUSED-OFF

Backup policies

The $HOME filesystem is guaranteed by daily backups. In the following the standard backup policies are reported; in particular cases, a different agreement is possible: contact the HPC support (superc@cineca.it) for further details.

...

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%

This may be tricky to interpret. OFFLINE area is the DRES data that has been stored on tape, after 3 months of storage (see DRES description above). ONLINE area is the DRES data still in FS or ARCH area. The total quota of storage capability assigned to your DRES is indicated in the "aQTA" parameter of the line "OFFLINE". When DRES is empty, the corresponding value of the line "ONLINE" will be the same as "OFFLINE", but when files begin to be moved it will decrease, while the "aUSED" parameter of OFFLINE will increase accordingly. It means that you have less space that you can use to store your data, since some of the already used space has been moved to tape. Similarly, deleting offline data will decrease the aUSED parameter in OFFLINE, and increase the aQTA parameter in ONLINE of the same amount. The formula to remember is:

TOTAL DRES STORAGE = aQTA-OFF = aQTA-ON + aUSED-OFF

File permissions

$WORK and $DRES are environmental variables, automatically set in the user environment.

$WORK variable points to a directory (fileset) specific for one of the user projects:

/gpfs/work/<account_name>

$DRES variable points to a space where all of the dres are defined:

/gss/gss_work/

In order to use a specific dres type the following path:

$DRES/<dres_name>

The owner of the root directory is the "Principal Investigator" (PI) of the project or the "owner" of the DRES, the group corresponds to the name of the project or the name of the DRES. Default permissions are:

own: rwx
group: rwx
other: -

In this way all project collaborators, sharing the same project group, can read/write into the project/dres fileset, whereas other users can not.

Users are advised to create a personal subdirectory under $WORK and $DRES. By default, files into the subdirectory are private, but the owner can easily share the files with the other collaborators by opening the subdirectory:

chmod 777 mydir
chmod 755 mydir

Since the $WORK/$DRES fileset is closed to non collaborators, the data sharing is active only among the project collaborators.

Pointing $WORK to a different project: the chprj command

The user can modify the project pointed to by the variable $WORK using the "change project" command.

To list all your accounts (both active or completed) and the default project:

chprj -l

To set $WORK to point to a different <account_no> project:

chprj -d <account_no>

More details are in the help page of the command:

chprj -h
chprj --help

Endianness

Endianness is the attribute of a system that indicates whether integers are represented from left to right or right to left. At present all CLusters in CIneca are "little-endian".

...

A comprehensive discussion on how to manage your data is presented can be found in a specific document.

...

Page tree

Versions Compared

Old Version 16

New Version 17

Key

Environment variables

Backup policies

Environment variables

Summary

Summary

Backup policies

File permissions

Pointing $WORK to a different project: the chprj command

Endianness

Page tree

Page History

Versions Compared

Old Version 16

New Version 17

Key

Environment variables

Backup policies

Environment variables

Summary

Summary

Backup policies

File permissions

Pointing $WORK to a different project: the chprj command

Endianness