Page tree
Skip to end of metadata
Go to start of metadata

Storage Overview

After logging in to Ginsburg you will be in your home directory. This home directory storage space (50 GB) is appropriate for smaller files, such as documents, source code, and scripts but will fill up quickly if used for data sets or other large files.

Ginsburg's shared storage server is named "burg", and consequently the path to all home and scratch directories begins with "/burg". Your home directory is located at /burg/home/<UNI>. This is also the value of the environment variable $HOME.

Each group account on Ginsburg has an associated scratch storage space that is at least 1 terabyte (TB) in size.

Note the important "No backups" warning regarding this storage at the bottom of this page.

Your group account's scratch storage is located under /burg/<ACCOUNT>. The storage area for each account is as following:


Default User Quota


50 GB













/burg/free64 GB
















/burg/ocpOCP shared volume with per user 10 TB quota.
/burg/rent128 GB






The amount of data stored in any directory along with its subdirectories can be found with:

cd <directoryName>
du -sh .

If you have lots of files in the directory, please allow some time for the 'du' command to return with its output.

User and Project Scratch Directories

Ginsburg users can create directories in their account's scratch storage using their UNI or a project name.

$ cd /burg/<ACCOUNT>/users/
$ mkdir <UNI>

For example, an astro member may create the following directory:

$ cd /burg/astro/users/
$ mkdir <UNI>

Alternatively, for a project shared with other users:

$ cd /burg/astro/projects/
$ mkdir <PROJECT_NAME>

Naming conventions (such as using your UNI for your users directory) are not enforced, but following them is highly recommended as they have worked well as organization mechanisms on previous clusters.

No Backups

Storage is not backed up. User files may be lost due to hardware failure, user error, or other unanticipated events.

It is the responsibility of users to ensure that important files are copied from the system to other more robust storage locations.

  • No labels