Q: How can I get my Quota

info.sh -q 

Q: I don't have the right permissions for the directory /albedo/work/projects/<a_project>

Project folders are not managed from the HPC itself, but from the AWI Cloud projects: https://cloud.awi.de/

You'll need to request access to the project, and the responsible person will have to approve (see HPC Data Policy and Projektordner / cloud.awi.de for more info about data projects):

1. Log in here with your AWI username and password: https://cloud.awi.de/#/login?redirect=/projects

2. In the search bar, search for the project name (remove the p_ at the front)

3. In the project click on "Request Membership"

4. Wait for the project owner to approve the person joining the data project.

Q: How can I avoid receiving "group correction" notifications on my email?

A: This notifications occur in most of the cases because a file's group ownership in one of the Albedo projects (/albedo/work/projects/p_my_project) has a discrepancy with the project's group. When you write a file in a folder, in most of the cases, the group ownership is taken from your primary group. That means writting a file in /albedo/work/projects/p_my_project instead of inheriting the p_my_project group as it should, it has my_primary_group:

$ cd /albedo/work/projects/p_my_project$ ls -la
1: total #
2: drwxr-xr-x 3 p_owner p_my_project 4096 Sep 21 16:49 .
3: drwxrws--- 6 root p_my_project 4096 Aug 10 15:00 ..
4: -rw-r--r-- 1 my_user my_primary_group 0 Sep 21 16:49 file1

An automatic tool fixes this for you for projects, so that project files follow the data project group convention, switching the my_primary_group of line 4 of the output to p_my_project, and then it's when you get an email notifying that the group of your file has changed.

While these notifications usually don't require immediate action, you can avoid them by setting your folder's setuid/setgid permission. In a nutshell that will ensure that any new file you write into your p_my_project directory will inherit its group.

  1. Note the x in line 2 of the output of ls -la above, this means that the current folder can be accessed (executed) by anyone in the p_my_project group. Instead of an x there should be an s which means it can be accessed by the group and setuid/setgid permission is set.
  2. If your folder does not belong to p_my_project group in the first place you can change that with
    $ chgrp p_my_project .
  3. Now set the setuid/setgid permission of the current folder
    $ chmod g+s .
    If you want to do this recursively into this folder add the -R flag to the chmod command.

The email notifications should stop for this folder. For more information about this please read about linux permissions, setuid/setgid, chmod... there is plenty of documentation on internet about it.

Q: I got an email about permissions on my $HOME and it was locked! What can I do?

We try to keep your folders safe from accidents by checking the permissions you have set. If you allow group/other to modify files in your HOME, we consider this unsafe, and set the permission to 000. When logging in, you'll get a permission error and won't be able to see your $HOME folder, but you can still re-enable read permissions! You just need to run:

$ chmod o+rx $HOME  # Note you need execute permission to do an ls!


  • No labels