titan

Up since 11/8/17 02:45 pm

eos

Up since 11/14/17 11:20 pm

rhea

Up since 10/17/17 05:40 pm

hpss

Up since 11/20/17 09:15 am

atlas1

Up since 11/15/17 07:25 am

atlas2

Up since 11/27/17 10:45 am
OLCF User Assistance Center

Can't find the information you need below? Need advice from a real person? We're here to help.

OLCF support consultants are available to respond to your emails and phone calls from 9:00 a.m. to 5:00 p.m. EST, Monday through Friday, exclusive of holidays. Emails received outside of regular support hours will be addressed the next business day.

Filesystems Available to Compute Nodes on EOS

See this article in context within the following user guides: Eos

The Eos compute nodes can only see the center-wide Lustre filesystems (Atlas) which includes the $MEMBERWORK, $PROJWORK, and $WORLDWORK storage areas. Other storage spaces (User Home, User Archive, Project Home, and Project Archive) are not mounted on compute nodes.

Warning: Only $MEMBERWORK, $PROJWORK, and $WORLDWORK areas are available to compute nodes on Eos.

As a result, job executable binaries and job input files must reside within a Lustre-backed work directory, e.g. $MEMBERWORK/[projid]. Job output must also be sent to a Lustre-backed work directory.

Batch jobs can be submitted from User Home or Project Home, but additional steps are required to ensure the job runs successfully. Jobs submitted from Home areas should cd into a Lustre-backed work directory prior to invoking aprun. An error like the following may be returned if this is not done:

aprun: [NID 94]Exec /lustre/atlas/scratch/userid/projid/a.out failed: chdir /autofs/na1_home/userid
No such file or directory