FAQ
From FarmShare
(→Slurm) |
(→Why can't I submit jobs to the gpu partition?) |
||
Line 47: | Line 47: | ||
You must explicitly request GPU resources using the <code>--gres</code> option when you submit a job to the <code>gpu</code> partition. | You must explicitly request GPU resources using the <code>--gres</code> option when you submit a job to the <code>gpu</code> partition. | ||
- | <source lang="sh">sbatch --partition=gpu --gres=gpu:1</source> | + | <source lang="sh">sbatch --partition=gpu --qos=gpu --gres=gpu:1</source> |
See the <code>man</code> page for <code>sbatch</code> for more information. | See the <code>man</code> page for <code>sbatch</code> for more information. |
Revision as of 16:05, 12 April 2018
Contents |
Policy
No. FarmShare is not approved for use with high-risk data, including protected health information and personally identifiable information. Do not use FarmShare resources to store or process protected information.
Shell and Environment
How do I change my shell?
bash
is the default shell for most users, and should be the default shell for all new accounts. Older accounts may use tcsh
by default, instead. If you would like to change your shell for any reason you can send e-mail to srcc-support@stanford.edu. The bash
, zsh
, fish
, mksh
, and tcsh
shells are installed, but not all are equally well-supported.
FarmShare uses Stanford's central account infrastructure, so changing your shell on FarmShare will affect all other systems that use this infrastructure (for example, myth.stanford.edu
). Please acknowledge your understanding of this by including something like the following in the text of your request.
Please change my default shell to $SHELL. I understand that this is a global change and will affect not only FarmShare systems, but all other systems at Stanford that use the University's central account infrastructure.
Why does my shell exit when running the module
command?
An early version of the default tcsh
shell configuration set an option, printexitvalue
, that was in conflict with the Lmod configuration. This issue has been fixed for new users, but existing users may have configurations that still set printexitvalue
in ~/.tcshrc.set
. You can either edit this file to remove the statement, make the statement a comment (by prepending #
), or copy over a corrected version of the default file from /etc/skel
.
cp /etc/skel/.tcshrc.set ~
You can either log out and back in again, or run unset printexitvalue
once, to make the change take effect.
Storage
Where are my files?
FarmShare no longer uses AFS for users' home directories. AFS is still accessible on rice
systems, and you can access your AFS home directory using the convenience link, ~/afs-home
.
Why can't I access files in ~/afs-home
or /afs
?
AFS access requires valid Kerberos credentials and an AFS token. You can use the klist
and token
commands to view your existing credentials, if any; if you're having trouble accessing files in AFS, try re-authenticating.
kinit && aklog
See Advanced Connection Options for a suggested SSH configuration that can help reduce the occurrence of token issues at login.
Are my data backed up?
We take regular snapshots of data in your home directory (/home/$USER
) and may be able to recover lost or damaged files in some cases. Data in your AFS home directory (~/afs-home
) are backed up every night, and backups are kept for 30 days. The most recent backup is mounted at ~/afs-home/.backup
; if you need to recover data from an older backup you should submit a HelpSU request. Data stored on the scratch volume (/farmshare/user_data/$USER
) are not backed up and may be purged without warning.
Slurm
Why can't I submit jobs to the gpu
partition?
You must explicitly request GPU resources using the --gres
option when you submit a job to the gpu
partition.
sbatch --partition=gpu --qos=gpu --gres=gpu:1
See the man
page for sbatch
for more information.
Why can't I submit jobs to the bigmem
partition?
You must request at least 96GB of memory using the --mem
option when you submit a job to the bigmem
partition.
sbatch --partition=bigmem --mem=96G
See the man
page for sbatch
for more information.
Why are my jobs killed after 2 hours?
While the maximum runtime for jobs is 2 days (unless you are submitting a job using the long
quality-of-service), the default runtime is 2 hours. If your job requires more time to run you must request the additional time explicitly, using --time
. You can also request less time than the default.
Applications
Why does Gaussian 16 fail with error: "illegal instruction (core dumped)"?
Gaussian 16 requires a more recent CPU than is available on some FarmShare systems. You'll need to request a node with a compatible CPU when submitting Gaussian 16 jobs, or fall back to Gaussian 09 to run on any node. See module help gaussian/g16-a.03
for more information.
Why does the gview
command fail to start GaussView?
The gview
command is used to start the desktop version of VIM; use the gv
command to start GaussView (after loading the gaussview
module), instead.