Categories: Data Management
Print this article
The next generation center-wide scratch filesystem is now available. The new center-wide scratch filesystems are comprised of two Lustre filesystems: Atlas1 and Atlas2. Together they provide 30PB of capacity and greater than 1TB/s aggregate performance. The Atlas filesystems replaced the current Widow filesystems (/tmp/work, /tmp/proj).
This page lists changes and tips that should be noted when transitioning from Widow to Atlas.
Directory Structure Change
The Atlas filesystem is organized by project. Users and projects still have work (aka scratch) areas, respectively as they did on Widow, but these new work areas are now located under a project directory. Users on multiple projects now have multiple such areas, now referred to as Member Work areas. The following environment variables have been created to simplify access:
Old (Widow) New (Atlas)
/tmp/projPurge (Feb 14, 2014)
The Atlas filesystem is shared by all OLCF users. To help ensure that enough space is available to each user/project, we will begin purging the
$PROJWORK/[projid]areas of data that has not been accessed in over (90) days. The
$PROJWORK/[projid]quota has also been increased to 100TB.Please Note: Purge to begin February 14, 2014.
Widow Decommission (Jan 28, 2014)
The Spider filesystems known as Widow[1-3] became read-only on January 07, 2014. The filesystems was decommissioned on January 28, 2014. Users were responsible for moving all needed data from the Widow filesystem to the Atlas filesystems.
Where Is Atlas Mounted?
Atlas is currently mounted on all OLCF systems.
As a result of the new directory structure, we are no longer required to change permissions of your $MEMBERWORK directory. Users now have the ability to control permissions on their scratch directory to share data within the project.
Directory Structure Changes
The Atlas filesystem is organized by project. Users and projects still have work (aka scratch) areas, respectively as they did on Widow, but these new work areas are now located under a project directory. Users on multiple projects now have multiple such areas, now referred to as Member Work areas.
New Directory Structure
The following structure exists for each project on one of the Atlas filesystems:
[projid]/ scratch/[userid]/ (aka "Member Work") proj-shared/ (aka "Project Work") world-shared/ (aka "World Work")
|Member Work||Project Work||World Work|
|Description||Each project member has a scratch directory within the project’s directory.||Each project directory contains a scratch directory for sharing data within the project.||Each project categorized as not containing export control or proprietary data contains a scratch directory for sharing data outside the project.|
|Purpose||Batch job output/input||Data sharing within the project||Data sharing outside the project|
|Access||Users have the ability to control permissions on their scratch directory to share data within the project, but not outside the project.||The project shared directory is accessible by project members only. Users are not able to alter permissions on the project shared directory.||The world shared directory is accessible by all users. Users are not able to alter permissions on the world shared directory.|
|Purge||14 day||90 day||14 day|