One of the improvements of ARE is that it now shares a home directory with Gadi. As a result, your OOD home directory files will not be present in ARE. If you need any of these, please see the Copying OOD files to ARE page for more details.
If you have deleted files under an ARE session using the GUI file manager, you may find that they have been moved to a .Trash-nnnnn
directory at the top level of that filesystem - eg if I deleted /scratch/z00/dmo900/my-large-junk-file
using the file manager, it would be moved to somewhere under /scratch/z00/.Trash-14978
(The nnnnn part at the end of the directory is your numeric userid, which you can find by typing id -u
in a Gadi terminal).
Files in these directories often don't show up in the GUI file manager "trash" folder, so you may need to manually remove them (eg rm -r /scratch/z00/.Trash-14978
in a terminal window - do be careful!)
This issue may be caused by exceeding the /home file system quota on Gadi. You will be able to confirm this by executing the quota -s command on Gadi's login node. If this is the case, deleting files from your Gadi's HOME directory to keep the usage below the quota may resolve your issue.
You will be able to see the usage of Gadi's HOME using the du -h --max-depth=1 ~ command.
This issue is caused by exceeding the /home file system quota on Gadi. quota -s command on Gadi's login node will show the quota exceeding information. Deleting files from your Gadi's HOME directory to keep the usage below the quota will resolve your issue.
You will be able to see the usage of Gadi's HOME using the du -h --max-depth=1 ~ command.
This issue might be caused by either exceeding your job's requested JOBFS size or walltime amount.
The $HOME/ondemand/data/sys/dashboard/batch_connect/sys/jupyter/ncigadi/output/<session_ID>/output.log file on Gadi will tell you the real reason.
Re-launching the JupyterLab session by either requesting more walltime or jobfs (available under the "Advanced options ..."), based on the cause of the issue, may resolve your issue.
If your issue is not solved above, please follow these instructions to report the issue: