Wiki DIFA

Strumenti Utente

Strumenti Sito

Ti trovi qui: start » oph » cluster » storage
oph:cluster:storage

Differenze

Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.

Link a questa pagina di confronto

Entrambe le parti precedenti la revisioneRevisione precedente
Prossima revisione		Revisione precedente
oph:cluster:storage [2024/10/22 07:37] – [/home/] aggiunte info quota diego.zuccato@unibo.itoph:cluster:storage [2025/02/06 16:07] (versione attuale) – [/home/] nuovo sito per /home/web diego.zuccato@unibo.it
Linea 10: Linea 10:
   * **/home/work**: Used as a work area for jobs that do not need very big datasets or need to have lots of files in a single directory (not recommended since this might degrade performances for all users!). **Per-sector quota** of 1TB (soft) / 2TB (hard).   * **/home/work**: Used as a work area for jobs that do not need very big datasets or need to have lots of files in a single directory (not recommended since this might degrade performances for all users!). **Per-sector quota** of 1TB (soft) / 2TB (hard).
  
-  * **/home/web**: web access is read-only and it is not possible to create dynamic pages. This space is web-accessible at ''https://apps.difa.unibo.it/files/people/Str957-cluster''.  **Per-sector quota** of 1TB (soft) / 2TB (hard) except astro with 4.4TB/7TB.+  * **/home/web**: 
 +    * This space is web-accessible at ''https://cluster.difa.unibo.it'' (and also from old ''https://apps.difa.unibo.it/files/people/Str957-cluster'' via an automatic redirect). 
 +    * web access is read-only and it is not possible to create dynamic pages. 
 +    * **Per-sector quota** of 1TB (soft) / 2TB (hard) except astro with 4.4TB/7TB. 
 +    * Requires either index.html or .htaccess file with ''Options: +Indexes'' to be browseable
  
-=== Technical characteristics ===+==== Technical characteristics ====
  
   * NFS-mount via Ethernet (1Gbps which is not very fast but quite responsive);   * NFS-mount via Ethernet (1Gbps which is not very fast but quite responsive);
Linea 21: Linea 25:
 This is the fast Input/Output area to be used for direct read/write operations from the compute nodes. There is no quota in this area, but an automatic cleaning procedure is enforced on all files older than 40 days to avoid the disk space being exhausted, as this would make running jobs crash when trying to write outputs on disk. Therefore, once your jobs are finished you are recommended to archive the relevant data to ''/archive/'' (see below) to avoid any data loss;  This is the fast Input/Output area to be used for direct read/write operations from the compute nodes. There is no quota in this area, but an automatic cleaning procedure is enforced on all files older than 40 days to avoid the disk space being exhausted, as this would make running jobs crash when trying to write outputs on disk. Therefore, once your jobs are finished you are recommended to archive the relevant data to ''/archive/'' (see below) to avoid any data loss; 
  
- +:!: folders inside sectors areas **must** use the account as name or you won't get important mails => possibe data loss. 
-=== Technical characteristics: ===+==== Technical characteristics: ====
  
   * Parallel filesystem, for quick (SSD-backed) access to the data you are working on;   * Parallel filesystem, for quick (SSD-backed) access to the data you are working on;
Linea 33: Linea 37:
 This is the main archive area to be used for large files, big datasets or archives; it is designed to be a distributed storage area for long-term data preservation. Data in this area should be stored in the form of compressed folders because the presence of a large number of small files will compromise its functionality. Every sector or project has a dedicated area with an associated quota on ''/archive/'', and when the quota is exceeded no further writing is possible on the sector or project area. This is the main archive area to be used for large files, big datasets or archives; it is designed to be a distributed storage area for long-term data preservation. Data in this area should be stored in the form of compressed folders because the presence of a large number of small files will compromise its functionality. Every sector or project has a dedicated area with an associated quota on ''/archive/'', and when the quota is exceeded no further writing is possible on the sector or project area.
  
- +:!: folders inside sectors areas **must** use the account as name or you won't get important mails => possibe data loss. 
-=== Technical characteristics: ===+==== Technical characteristics: ====
  
   * **To not be used to store a large number of small files**, this will compromise the functionality of the storage space eventually blocking all the reading/writing operations of the entire cluster.   * **To not be used to store a large number of small files**, this will compromise the functionality of the storage space eventually blocking all the reading/writing operations of the entire cluster.
Linea 40: Linea 44:
   * Read-only access from compute nodes, read/write only from frontends and filetransfer nodes   * Read-only access from compute nodes, read/write only from frontends and filetransfer nodes
   * Quota imposed (both on file size and number of files) per sector, with extra space allocated for specific projects (in /archive/projects) or bought by individuals (in /archive/extra).   * Quota imposed (both on file size and number of files) per sector, with extra space allocated for specific projects (in /archive/projects) or bought by individuals (in /archive/extra).
- +  * Currently ACLs (setfacl) are notsupported (cephfs exported via NFS-Ganesha does not allow to set/get ACLs) 
- +==== Monitoring system of space usage ====
-====== Monitoring system of space usage ======+
  
 To allow users/sectors/projects to handle their /archive/ storage and avoid their sector going over quota, a monitoring and alerting system is now in place. Some of you may have already received alerting emails from the OPH cluster last night, around midnight. These emails are meant to inform you about your usage of the /archive/ system and alert you in case your sector/project is already over quota (i.e. using more than 100% of the allowed space or number of files, so that writing is already blocked) or close to the quota limit (i.e. using more than 90% of either the available space or number of files). To allow users/sectors/projects to handle their /archive/ storage and avoid their sector going over quota, a monitoring and alerting system is now in place. Some of you may have already received alerting emails from the OPH cluster last night, around midnight. These emails are meant to inform you about your usage of the /archive/ system and alert you in case your sector/project is already over quota (i.e. using more than 100% of the allowed space or number of files, so that writing is already blocked) or close to the quota limit (i.e. using more than 90% of either the available space or number of files).
Linea 56: Linea 59:
 Every node does have some available space on local storage in ''$TMPDIR''. This can be used to store temporary files that do not need to be shared between nodes. Being a local memory, latency is very low and with a limited capacity, usually around 200GB. It it automatically cleaned when the job terminates. Every node does have some available space on local storage in ''$TMPDIR''. This can be used to store temporary files that do not need to be shared between nodes. Being a local memory, latency is very low and with a limited capacity, usually around 200GB. It it automatically cleaned when the job terminates.
  
 +==== Technical characteristics: ====
 +
 +  * local space: not shared between multiple nodes, not even for a single multi-node job
 +  * quite fast
 +  * automatically cleaned when job ends
  
oph/cluster/storage.1729582672.txt.gz · Ultima modifica: 2024/10/22 07:37 da diego.zuccato@unibo.it
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki