Page Comparison

2017-10-31: Home and Project Directory Structure Rearrangement

Previously, each user had a /home/<USER>/ directory for their personal configuration files and data.  With this change, each user will have a /projects/<PIRG>/<USER>/ directory for data, with /home/<USER>/ used just for configuration (and other relatively small) files. 

In addition, each PIRG's shared project directory, which previously resided in /projects/<PIRG>/, is now in /projects/<PIRG>/shared/.

With these changes, all directories under a PIRG's /projects/<PIRG>/ share the same large quota pool, typically multiple TB.  Each /home/<USER>/ directory now has a much smaller quota, currently 10GB.

In order to facilitate migration to the new layout, the contents of each home directory will be moved to the new location (/projects/<PIRG>/<USER>/).  However, copies of the top-level dot files (e.g., .bashrc) will be left in /home/<USER>/ as well.  For most users, everything will just work as before.  In a few cases, where a hard-coded path was used or dot files are including non-dot files, manual changes might be necessaryTalapas is a cluster of Linux systems, so file structure on Talapas follows the typical structure you’d find on a standard Linux system. As a user, there are several locations in which to store your data on Talapas:

Home

Your home directory at /home/<username> has a quota of 250GB and can be used to store whatever work-related data you might need. This directory is only accessible by you.

Projects

For each project you’re a part of, you have a /home/<project> symlink in your home directory to /projects/<project>. This project directory is owned by the PI and all members of the PIRG have read/write access to files and directories created here to enable collaboration. By default, the project has a 2TB quota and can be increased by purchasing additional storage.

For example, here is my home directory. Notice the symlink from racs to /projects/racs.

[lcrown@login1 ~]$ ls -l
total 11
drwxr-xr-x. 2 lcrown uoregon 4096 Dec  6  2023 Desktop
drwxr-xr-x. 3 lcrown uoregon 4096 Jan  2  2024 Documents
drwxr-xr-x. 2 lcrown uoregon 4096 Dec  6  2023 Downloads
drwxr-xr-x. 5 lcrown uoregon 4096 Apr 25 09:14 globus
drwxr-x---. 3 lcrown uoregon 4096 May 22  2023 matrix_mul
drwxrwxr-x. 2 lcrown uoregon 4096 Dec  5  2023 mpitest
drwxr-xr-x. 3 lcrown uoregon 4096 Jul 29  2020 ondemand
lrwxrwxrwx. 1 lcrown uoregon   14 Aug 21 15:56 racs -> /projects/racs
-rw-r--r--. 1 lcrown uoregon   10 Mar  5 14:16 success.txt
drwxr-xr-x. 2 lcrown uoregon 4096 May  6 12:56 temp
-rw-r--r--. 1 lcrown uoregon    0 Apr 22 14:52 testfile
-rw-r--r--. 1 lcrown uoregon  104 Feb  7  2024 test.go
-rw-r--r--. 1 lcrown uoregon  114 Aug 10  2023 test.yml
-rw-r--r--. 1 lcrown uoregon 1437 Nov  9  2023 Untitled.ipynb
-rw-r-----. 1 lcrown root     563 Sep 25  2023 wavedecompnet.yml

I can navigate to my racs project via the symlink:

[adm-lcrown@login1 ~]$ cd racs
[adm-lcrown@login1 racs]$

Or via the direct path:

[adm-lcrown@login1 ~]$ cd /projects/racs
[adm-lcrown@login1 racs]$

This directory is where I can store my files for collaboration with other users on the project.