FAQ: Difference between revisions

From bwHPC Wiki
Jump to navigation Jump to search
mNo edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
__TOC__
__TOC__


== Access and Account Issues ==
== FAQ bwUniCluster ==


'''Q: I see 'Status: LOST_ACCESS' when I check the [https://login.bwidm.de/user/index.xhtml Registry info] of my service?'''
=== I see 'Status: LOST_ACCESS' in the Registry Info ===
A: Please check [https://login.bwidm.de/user/index.xhtml Personal data] if you are still a valid user and verify entitlement <code><nowiki>http://bwidm.de/entitlement/bwUniCluster</nowiki></code>. Otherwise please check if you answered the [[BwUniCluster_2.0_User_Access#Step_C:_Fill_out_the_bwUniCluster_questionnaire|Questionnaire]].


Answer:


You need to fulfill the requirements outlined in
== FAQ bwForCluster ==
* BwUniCluster: [[Registration/bwUniCluster]]
* BwForCluster: [[Registration/bwForCluster]]


In short: your "Entitlement"
'''Q: I see 'Status: LOST_ACCESS' when I check the 'Registry info' of my service?'''
* BwUniCluster: you need the [[bwUniCluster Entitlement|Registration/bwUniCluster/Entitlement]]
A: Please check 'Personal data' if you are still a valid user and verify entitlement <code><nowiki>http://bwidm.de/entitlement/bwForCluster</nowiki></code>. Otherwise please check if you are still a member of a 'Rechenvorhaben'. [[bwForCluster User Access]] for more information and links to bwForCluster registration pages.
* BwForCluster: you need the [[bwForCluster Entitlement|Registration/bwForCluster/Entitlement]]
See the two links above to learn how to check if you have the entitlement.

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

In case the entitlement is present:

* BwUniCluster: Check if you answered the [[BwUniCluster_2.0_User_Access#Step_C:_Fill_out_the_bwUniCluster_questionnaire|Questionnaire]].
* BwForCluster: Check if you are an active [https://zas.bwhpc.de/shib/info_rv.php 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
<code>
du -hs .[!.]* * | sort -h | tail
</code>

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

<code>.[!.]*</code> makes sure the "hidden" dot files are also checked.

* Inodes:

<code>
du -s --inodes .[!.]* * | sort -n
</code>

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:

<code>
ls -1a | wc -l
</code>

Latest revision as of 10:45, 28 January 2026

Access and Account Issues

I see 'Status: LOST_ACCESS' in the Registry Info

Answer:

You need to fulfill the requirements outlined in

In short: your "Entitlement"

See the two links above to learn how to check if you have the entitlement.

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

In case the entitlement is present:

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