Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
habrok:data_management:storage_areas [2023/04/11 14:44] – [/local] adminhabrok:data_management:storage_areas [2025/05/20 14:09] (current) – [/scratch] Add link to Many File Jobs page pedro
Line 15: Line 15:
 ===== /scratch ===== ===== /scratch =====
  
-Each user of the system also has a directory in ''/scratch'', which is meant for storing large amounts of data that needs to be processed. **Please be aware that backups of this data are not made, and that /scratch is not meant for long term data storage.** This means that you have to copy important data to other storage yourself. This storage can for example be the ''/projects'' or RDMS storage system. +Each user of the system also has a directory in ''/scratch'', which is meant for storing large amounts of data that needs to be processed. **Please be aware that backups of this data are not made, and that, because of this, /scratch is not suitable for long term data storage.** This means that you have to copy important results to other storage yourself regularly. This storage can for example be the ''/projects'' or RDMS storage system. 
  
 Also on ''/scratch'' quotas are applied to prevent the system from running out of space. Currently the limit is 250GB by default. If this limit is too low for your research purposes, you can request us to change this limit. The limit can be increased to a "fair use" value without issues. When more space is required it is expected that ''/scratch'' is still only used as a staging area for data that will immediately be processed, and that a suitable storage system is available elsewhere for storing the full data collection. These storage systems can again be the ''/projects'' or RDMS systems described below. Also on ''/scratch'' quotas are applied to prevent the system from running out of space. Currently the limit is 250GB by default. If this limit is too low for your research purposes, you can request us to change this limit. The limit can be increased to a "fair use" value without issues. When more space is required it is expected that ''/scratch'' is still only used as a staging area for data that will immediately be processed, and that a suitable storage system is available elsewhere for storing the full data collection. These storage systems can again be the ''/projects'' or RDMS systems described below.
Line 23: Line 23:
 There is also a limit on the number of files that can be stored. This to reduce the load on the file system metadata server, which keeps track of the data about files (time of access, change, size, location, etc.). Handling a huge number of files is a challenge for most shared file systems and accessing a huge amount of files will lead to performance bottlenecks. There is also a limit on the number of files that can be stored. This to reduce the load on the file system metadata server, which keeps track of the data about files (time of access, change, size, location, etc.). Handling a huge number of files is a challenge for most shared file systems and accessing a huge amount of files will lead to performance bottlenecks.
  
-The best way of handling data sets with many (> 10,000) files is to not store them on /scratch as is, but as (compressed) archive files. These files can then be extracted to the fast local storage on the compute nodes at the beginning of a job. +The best way of handling data sets with many (> 10,000) files is to not store them on /scratch as is, but as (compressed) archive files. These files can then be extracted to the fast local storage on the compute nodes at the beginning of a job. You can find more details and examples in our dedicated [[habrok:advanced_job_management:many_file_jobs|page]] on this topic.
  
 When the processing is performed on the fast local storage the job performance will be much better. When the processing is performed on the fast local storage the job performance will be much better.
Line 61: Line 61:
 ===== /projects ===== ===== /projects =====
  
-On the login nodes each user will have storage space in ''/projects''. This storage area is meant for storing data for a longer period. It cannot be reached by the compute nodes as it is not optimized for processing data.+On the login/interactive nodes each user will have storage space in ''/projects/$USER''. This storage area is meant for storing data for a longer period. It can only be accessed on the login and interactive nodes and cannot be reached by the compute nodes as it is not optimized for processing data.
  
 By default 250GB is allocated. This space can be increase upon request, based on a "fair use" principle. Above a certain threshold payment for the space will be required. By default 250GB is allocated. This space can be increase upon request, based on a "fair use" principle. Above a certain threshold payment for the space will be required.