Storage for "compute" related servers

EIT provides access to a number of EIT- and Campus-managed servers for light simulation computing. Below are descriptions of these "compute" servers and the storage options available for them.

Linux Servers

Types of Linux servers 

  • Glue general shared servers (compute.ece.umd.edu, login.math.umd.edu, compute.physics.umd.edu, etc.)
    • This is a small set of older servers that is not meant for research computing.  It is more focused on teaching and basic tasks.  If you run compute heavy jobs and impact others, you will be asked to cease and may be barred from accessing the servers if you continue.
    • No GPUs.
    • Very, very limited local space that is not backed up.

  • Glue, Faculty-specific servers
    • Some faculty have their own server(s) specific to their research groups.
    • Some have GPUs.
    • Some have significant local storage that is not backed up.  File server access is available on most Glue servers.  Some faculty have NAS devices or central storage that they pay for which can be mapped to these servers.

  • Non-glue, Faculty-specific servers
    • Some faculty have their own server(s) specific to their research groups.
    • Some have GPUs.
    • Some have significant local storage that is not backed up.  File server access is not available.  Some faculty have NAS devices or central storage that they pay for which can be mapped to these servers.

Linux Server Storage Information

  • File server - User "homespace"
    • Available on Glue servers only. 
    • Default location for your files.
    • Backed up nightly.
    • Limited to 5 GB unless you pay for additional space.  Run "fs lq -human" to see your quota in human readable (not so many zeroes to look at) format.

  • File server - Shared or Software Space
    • Available on Glue servers only. 
    • Some groups have additional file server locations that are usually for software but can be used for other purposes.
    • Backed up nightly.
    • Quota can vary but anything significant will be paid for by the research group.  Run "fs examine <directory path>" to see the quota.  There isn't a human readable option here.  If you see 8000000, that's 8 GB as a reference.
  • Faculty-specific servers - Local space
    • Generally, this is located in /export/<your username> on faculty specific servers.  This is not available on general, shared servers.
    • Is not backed up. Data loss can occur if you accidentally delete something or there is a hardware issue.
    • The size of this will vary and is usually shared space with everyone on the server.  Run "df -h" to see the disk layout.  If /export isn't specifically referenced, it is usually under the main "/" partition.

  • "/tmp"
    • This directory is named this way because it is temporary.  Expect all data stored here to be wiped out on every reboot.
    • Is not backed up. Data loss can occur if you accidentally delete something or there is a hardware issue.
    • The size of this varies per server.  Run "df -h" to see the disk layout.  If /tmp isn't specifically referenced, it is usually under the main "/" partition.

 

Windows Servers

Types of Windows Servers

  • There are no generally shared, publicly-available Windows research servers available. Only departmental Staff shared servers are managed for UMD Staff. 

  • Faculty specific servers:
    • Some faculty have their own server(s) specific to their research groups.
    • Some have GPUs.
    • Some have significant local storage that is not backed up.  File server access is available in relatively small sizes and at cost.  Some faculty have NAS devices or central storage that they pay for which can be mapped to these servers.

Windows Servers Storage Information

  • File server space
    • Backed up regularly.
    • Relatively small amounts are available at cost.

  • Local space
    • Location varies.
    • Is not backed up. Data loss can occur if you accidentally delete something or there is a hardware issue.
    • The size will vary and is usually shared space with everyone on the server.



Keywords:
afs glue terpconnect compute linux ubuntu research storage 
Doc ID:
162619
Owned by:
Jeff M. in Engineering IT
Created:
2026-07-14
Updated:
2026-07-14
Sites:
University of Maryland Engineering IT