FAQ

Access and Account Issues: bwUniCluster

Q: I Cannot Log In to my bwUniCluster and See 'Status: LOST_ACCESS' in the Registry Info

A: You need to fulfill the requirements outlined in → Registration/bwUniCluster

Please check which of those two things are missing using the following documentation:

Entitlement

You need the Registration/bwUniCluster/Entitlement

If the entitlement is missing: please check with the local support of your home university (the university where you study or are employed)

Questionnaire

→ Check if you answered the Questionnaire.

Access and Account Issues: bwForCluster

Q: I Cannot Log In to my bwForCluster and See 'Status: LOST_ACCESS' in the Registry Info

A: You need to fulfill the requirements outlined in

→ Registration/bwForCluster

Please check which of those two things are missing using the following documentation:

Entitlement

You need the Registration/bwForCluster/Entitlement

If the entitlement is missing: please check with the local support of your home university (the university where you study or are employed)

ZAS Permission

→ Check if you are an active member of a compute activity and the "RV" hasn't expired.

Storage and File Systems

I am over the File System Quota

There are two resources with limits enforced by quota:

• disk space
• number of inodes (files).

It is important to identify the main sources that consume these resources.

• Size: List all directories (and files) in your home directory or workspace sorted by size

du -hs .[!.]* * | sort -h | tail

Descend in a directory with a large reported size and repeat until you find large files that are worth taking care of.

.[!.]* makes sure the "hidden" dot files are also checked.

• Inodes:

du -s --inodes .[!.]* * | sort -n

This will only count inodes in subdirectories. Also make sure your top-level (e.g. $HOME) directory aren't full with hundred thousands of files:

ls -1a | wc -l