Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. What Disks to Use
  2. How to Copy Files to/from Hydra
  3. Disk Quotas
  4. Disk Configuration
  5. Disk Usage Monitoring
  6. NetApp Snapshots: How to Recover Old or Deleted Files
  7. Public Disks Scrubber
  8. SSD and Local Disk Space

Anchor
WhatDisks
WhatDisks
1. What Disks to Use

...

Anchor
DiskConfig
DiskConfig
4. Disk Configuration

 



 MaximumQuotas per userNetApp 

 diskdisk space

no. of files

snapshots 

Disk name

capacity

soft/hard

soft/hard

enabled?

Purpose

/home

10TB

50/100GB

1.8/2M

yes: 4 weeks

For your basic configuration files, scripts and job files

- your limit is low but you can recover old stuff up to 4 weeks.

/data/sao

or

/data/nasm

40TB*

1.9/2.0TB

4.75/5M

yes: 2 weeks

 For important but relatively small files like final results, etc.

- your limit is medium, you can recover old stuff, but disk space is not released right away.

For SAO or NASM users.

/data/genomics

30TB*

0.45/0.5TB1.19/1.25M

yes: 2 weeks

For important but relatively small files like final results, etc.

- your limit is medium, you can recover old stuff, but disk space is not released right away.

For non-SAO/NASM users.

/pool/sao

or

/pool/nasm

37TB

1.9/2.0TB

4/5M

no

For the bulk of your storage

- your limit is high, and disk space is released right away, for SAO or NASM users.

/pool/genomics

50TB

1.9/2.0TB4.75/5M

no

For the bulk of your storage

- your limit is high, and disk space is released right away, for non-SAO users.

/pool/biology

7TB

1.9/2.0TB4.75/5M

no

For the bulk of your storage

- your limit is high, and disk space is released right away, for non-SAO/NASM users.

/scratch

100TB

9.5/10.0TB

23.75/25M

no

For temporary storage, if you need more than what you can keep in /pool

- SAO, NASM or non-SAO/NASM users should use

 /scratch/sao, /scratch/nasm or /scratch/genomics, respectively



    
 Project specific disks
/pool/kistlerl21TB20.0/21.0T49.9/52.5MnoNMNH/Logan Kistler
/pool/kozakk11TB10.5/11.0T26.1/27.5MnoSTRI/Krzysztof Kozak
/pool/nmnh_ggi21TB15.0/15.8T37.4/39.4MnoNMHN/GGI
/pool/sao_access21TB15.0/15.8TB37.4/39.4MnoSAO/ACCESS
/pool/sao_atmos36TB

 8.0/10TB

9/10MnoSAO/ATMOS
/pool/sao_rtdc10TB*2.8/3.0TB2.5/3.0MnoSAO/RTDC
/pool/sao_cga8TB7.9/8TB20/19MnoSAO/CGA
/pool/sylvain15TB14/15TB 63/65Mno

SAO/Sylvain Korzennik






Extra
/pool/admin10TB*5.7/6.0TB

14.3/15.0M

noSys Admin
/pool/galaxy15TB*10.7/11.3TB26.7/28.1MnoGalaxy

*: maximum size, disk size will increase up to that value if/when usage grows

...

No Format
nopaneltrue
% du -sh dir/
136M    dir/

 


The output of df can be very long and confusing.

...

No Format
nopaneltrue
% df -h /pool/sao
Filesystem           Size  Used Avail Use% Mounted on
10.61.10.1:/vol_sao   20T   15T  5.1T  75% /pool/sao

 


You can compile the output of du into a more useful report with the dus-report.pl tool. This tool will run du for you (can take a while) and parse its output to produce a more concise/useful report.

...

to see how else you can use it.

 


The tool disk-usage.pl runs df and presents its output in a more friendly format:

...

The format of this file is not very user friendly and users are listed by their user ID.

 


The Hydra-specific tools, (i.e., requires that you load the tools/local module):

...

for the complete usage info.

 


Users whose quotas are above the 75% threshold will receive a warning email one a week (issued on Monday mornings).

...