Skip to Main Content

The University of Tennessee

Newton header banner

Frequently Used Tools:



Home » Documentation » Cluster Storage

Cluster Storage

There are three classes of disk storage on the cluster: home directory, scratch, and project-associated mass storage.

Home directory

Home directory storage is located at /lustre/home. Storage use is limited to 40 GB per user by default but can be increased on request. This file system is globally available and is intended to house source code, binaries, and other relatively small files. Data in the home directories is backed up nightly (see Data Backup). Users may check their home directory utilization using the "quota" command: quota -v $USER.

Scratch space

There are two types of scratch space: local and global. Each worker node has a locally attached disk that is available for temporary storage during the execution of a job. The location of this directory is stored in the $TMPDIR environment variable. Available space is on the order of 100GB. Access to this space is only possible during the execution of the job on that compute node. Local scratch storage is not backed up.

Global scratch space is available at /lustre/scratch. This is a single storage space that is visible on all cluster nodes. To use this space you should create a subdirectory here using your username, and store files under this directory. Files which have not been modified in the past month may be automatically deleted from this storage location.

Project-associated mass storage

For computing projects that have large storage requirements we offer larger storage allocation on the Lustre filesystem (under the /lustre/projects/ directory), the Gluster filesystem (under /omega/), and NFS shares (under the /data/ directory). You may apply for use of this storage on the HPC web manager page. Backup of this data is available with special arrangements.

Special notes

The /data directory on cluster machines is a special mount point that is used by the autofs service. Directories that are located under this mount point may not be visible until an attempt is made to access them by either reading a file under the directory or using cd to enter the directory structure. This is because these directories are mounted on an as-needed basis.