Disk quota
Student users, and staff users with ‘GUID’-named accounts, have their home directories on brutha. Brutha is where your JupyterHub home directory is, so your ‘brutha quota’ is your Jupyter quota, too. See below.
Research group users typically have home directories on group-specific machines. These are managed on a group-specific basis: talk to your group IT support.
brutha §
Disk quotas are enabled on brutha – that is, there is a limit to how much disk space you are able to use. These quotas are currently set ‘lowish’: if you think you need more, talk to your class head or lab head, or your project supervisor (we won't take much persuading).
To see what your quota is, and how much of it you are using, go to your SSO identity page, enter your username and password where prompted, and you should see a line like
User sampleuser: using 21.0MiB on /local (4% of soft limit 500MiB, hard limit 600MiB).
This shows that user sampleuser is using only a very modest 21MB out
of a quota of 500MB. Usage may stray above this for a short time (a
few days), and the user is nagged about this; but if usage stays above
this for too long, or if it goes above the 600MB hard limit, then
further file writes are prohibited. The fix is to delete files.
If you are over your hard limit, or over the soft limit for too long, then you will be unable to write files and, as a side-effect, you will be unable to log in.
Unfortunately, JupyterHub is very un-graceful about you running out of quota. If you connect using ssh, you are warned when your quota is nearly exhausted; if you connect using JupyterHub, the first indication is an (apparently) end-of-the-world error message from JupyterHub.
If you are connected to brutha via ssh, then you can look at your quota using the command
brutha-mgt quota
and the command
du -m $HOME
will show you how much space is being used in various directories, in units of MB.