...
- Your home directory is in weka (/sdf/home/<first letter of your userid>/<your userid>) with 30 GB of space. This space is backed up and is where code, etc., should go.
- We have group space at /sdf/group/fermi/ which includes shared software, as well as Fermi-supplied user (i.e., on top of your home directory) and group space. You can find it in /sdf/group/fermi/u/<you>.
- after gpfs is retired in late 2023, this is where your larger user space will be.
- your user/group space on the old clusters is not directly accesible accessible from s3df - it currently needs to be copied over. (this access policy may get reversed soon)
- We're still providing additional user space from the old cluster, available on request via the slac-helplist mailing list. It is not backed up. This space is natively gpfs. User directories are available under: /gpfs/slac/fermi/fs2/u/<your_dir>; we have not created any group directories on s3df yet.
| Info | ||
|---|---|---|
| ||
If you were working on SDF, note that S3DF is completely separate (aside from the account name). Even though path names might look similar, they are on different file systems. You can still access all your SDF files by prepending "/fs/ddn/" to the paths you were used to. |
...
For generic advice on running in batch, see Running on SLAC Central Linux. Note that the actual batch system has changed and we have not updated the doc to reflect that. This is advice on copying data to local scratch, etc.
| Info | ||
|---|---|---|
| ||
You can run cronjobs in S3DF. Users don't have to worry about token expiration like on AFS. Select one of the iana interactive nodes (and remember which one!) to run on. Since crontab is per host (no trscrontab), if the node is reinstalled or removed, the crontab will be lost. It's probably best to save your crontab as a file in your home directory so that you can re-add your cronjobs if this happens: crontab -l > ~/crontab.backup Then to re-add the jobs back in: crontab ~/crontab.backup |