Your home directory is a place for you to store all your files and data related to your research. On the clusters, this home directory is shared between all the compute/execution systems and is created when you log in for the first time.
You home directory may be in one of three file systems depending on when your account was created. Newly created accounts will have their home directory in the Ceph file system (/mnt/ceph). Historically, some home directories may be in /mnt/lfs2 (Lustre).
New users’ (From Dec 2017 on) home directories will be in the new distributed file system Ceph (/mnt/ceph/
The other distributed file system available is Lustre (/mnt/lfs2/
file in that directory. The easiest way is simply to:
cd /mnt/lfs2/<username>/my_important_files/ touch .backup
The backup script will then know to rsync the contents of that directory. Please note that subdirectories are not backed up. Do not mark data otherwise stored in Ceph, or easily reproduced (such as software), for backup.
Important Note: The Lustre file system is the only distributed file system mounted by all the cluster nodes in the standard partitions. In general, to run analyses on the cluster (not standalones) your scripts and data files should reside in Lustre, and you should submit the job from there. We are working to get Ceph mounted on all the cluster nodes. You can keep your data in Ceph and run your job with the
-C "ceph" command line option to request nodes that have the /mnt/ceph directory. For example :
sbatch -C "ceph" myjob.slurm
|Greatest||Moderate||Data stored in triplicate, regular backups stored offsite|
|Withstands disk failures||Moderate||Opt-in backup|
Each home directory contains configuration files associated with specific programs. Some of these include:
This is your configuration file for the bash shell which is read when a user requests an interactive shell. You can change this to add aliases, functions, change your shell prompt, load modules, and run specific programs when you start an interactive shell.
This file is updated by bash upon logout and contains a history of all the commands you have run during your system. Even if you are a big privacy advocate and do not want the admins to see what you are doing, I recommend keeping the file intact, as it is a useful tool for the admins to help debug any issues you may be having.
This is your emacs configurations file. Edit this file to change your emacs configuration.
This is your Vi IMproved configuration file. Edit this file to change the behavior of vi/vim.