...
By default, users are assigned one core at a time, and a chunk of memory (~4GB RAM) associated with that core. For many applications, this may not be enough memory. To get around this, one can reserve more cores:
[user@ln1 user@talapas-ln1 ~]$ srun -n28 --pty bash
This will reserve all 28 cores on a basic node, which should suffice for most applications. Alternatively, if you just want to reserve more memory, do:
[user@ln1 user@talapas-ln1 ~]$ srun --mem=50G --pty bash
...
How-to view Talapas compute usage
9. "I have exceeded my disk quota, can you increase it?"
Most quota issues involve the home directory. All users gets a hard 10GB quota that is fixed and will not be increased. We recommend that users use their project directory (/projects/{myPIRG}/{myUsername}) to write and store their data. By default, PIRGs have minimum of 2 TB to work with in their project directories, and users have a shortcut in their home directory that points to their projects directory so that it can be accessed from the home directory by just doing "cd projects". If you do not have this shortcut and would like to have it, perform the following commands:
[user@talapas-ln1 ~]$ cd
[user@talapas-ln1 ~]$ ln -s /projects/myPIRG/myUsername projects
[user@talapas-ln1 ~]$ cd projects
[user@talapas-ln1 projects]$
You can now work from your projects folder.
Your project usage and your PIRGs usage and quota are displayed on login. Your project quota is a soft quota - if your group's project quota has been exceeded, your group will have a 30 day grace period to bring it back under the quota. If that does not happen, it becomes a hard quota and no new files can be created or stored. If that becomes the case and your group needs your project quota increased, let us know at racs@uoregon.edu.