IMPORTANT: The /tigress storage system is closing in on end of life. Quotas have been reduced for most users. The plan is to make both /tigress and /projects read-only on the cluster nodes in the near future (months). This is in preparation for the new system, TigerData, which will be replacing /projects and /tigress.


The /tigress filesystem is a large, shared filesystem, available on the head and compute nodes of the large clusters and Tigressdata. See the Data Storage page for a complete description of all the filesystems.

Space usage is restricted on /tigress. For users with access to these systems, an application for space beyond the default quota of 500 GB may be made via the quota request form. Some users will have access to /projects and not /tigress and vice versa. Read the Data Storage page for more details.

The implementation of this filesystem uses GPFS (General Parallel File System), an IBM commercial filesystem specifically designed to support high reliability and computing clusters. There is 6.5 PB of space allocated to /tigress. The data and files on /tigress are backed up if you need to recover your files.

Only the latest copy of any file residing on /tigress is kept on the server, no previous versions of a file are kept. These active files are kept on the backup server indefinitely. Should a file be deleted from /tigress, it will remain on the backup server for 10 days after which it will be deleted from the backup server. 

/tigress is not suitable to use as scratch disk or as a home filesystem.