FSx Lustre Filesystems
The Odin cluster has multiple FSx Lustre filesystems with Data Repository Associations (DRAs) configured with auto-import/export enabled.
Filesystem 1: /mnt/odin (12TB)
Main HPC storage for legacy data and Kamino output buckets.
| S3 Bucket | FSx Mount Point | Auto-Sync |
|---|---|---|
s3://qcs-training-data |
/mnt/odin/qcs-training-data |
✅ |
s3://produsw2-bora-dev-data-kamino |
/mnt/odin/produsw2-bora-dev-data-kamino |
✅ |
s3://az-new-legacy-data |
/mnt/odin/az-new-legacy-data |
✅ |
s3://az-bora-legacy-data-transfer |
/mnt/odin/az-bora-legacy-data-transfer |
✅ |
s3://prod-usw2-redcap-balid.../output |
/mnt/odin/qcs-bali-dev-output |
✅ |
s3://prod-usw2-redcap-cldng.../output |
/mnt/odin/qcs-cldn-gea-dev-output |
✅ |
s3://prod-usw2-redcap-folr1.../output |
/mnt/odin/qcs-folr1-ov-dev-output |
✅ |
s3://prod-usw2-redcap-odinq.../output |
/mnt/odin/qcs-odin-dev-output |
✅ |
Filesystem 2: /mnt/qcs (1.2TB)
New Navify buckets for ingest and output.
| S3 Bucket | FSx Mount Point | Auto-Sync |
|---|---|---|
s3://qcs-bali-dev-ingest |
/mnt/qcs/qcs-bali-dev-ingest |
✅ |
s3://qcs-bali-dev-output |
/mnt/qcs/qcs-bali-dev-output |
✅ |
s3://qcs-cldn-gea-dev-ingest |
/mnt/qcs/qcs-cldn-gea-dev-ingest |
✅ |
s3://qcs-cldn-gea-dev-output |
/mnt/qcs/qcs-cldn-gea-dev-output |
✅ |
s3://qcs-folr1-ov-dev-ingest |
/mnt/qcs/qcs-folr1-ov-dev-ingest |
✅ |
s3://qcs-folr1-ov-dev-output |
/mnt/qcs/qcs-folr1-ov-dev-output |
✅ |
s3://qcs-odin-dev-ingest |
/mnt/qcs/qcs-odin-dev-ingest |
✅ |
s3://qcs-odin-dev-output |
/mnt/qcs/qcs-odin-dev-output |
✅ |
Filesystem 3: /mnt/gxp (1.2TB)
GxP-compliant data storage. Data managers only.
- Throughput: 200 MB/s/TiB
- Linux Mount:
/mnt/gxp(on data-manager-linux) - Windows Access:
\\data-manager-linux.odin.cluster.local\gxp
Filesystem 4: /mnt/ingest (9.6TB)
Kamino data migration ingress buckets. Data managers only.
| S3 Bucket | FSx Mount Point |
|---|---|
s3://kamino-automation-ingress |
/mnt/ingest/kamino-automation-ingress |
s3://kamino-config-ingress |
/mnt/ingest/kamino-config-ingress |
s3://kamino-ctd-ingress |
/mnt/ingest/kamino-ctd-ingress |
s3://kamino-ec-study-ingress |
/mnt/ingest/kamino-ec-study-ingress |
s3://kamino-edl-ingress |
/mnt/ingest/kamino-edl-ingress |
s3://kamino-internal-ingress |
/mnt/ingest/kamino-internal-ingress |
s3://kamino-labcorpncfab-ingress |
/mnt/ingest/kamino-labcorpncfab-ingress |
s3://kamino-paxgene-ingress |
/mnt/ingest/kamino-paxgene-ingress |
Viewing Files
From login nodes:
# FSx Filesystem 1 (/mnt/odin)
ls /mnt/odin/qcs-training-data/
ls /mnt/odin/produsw2-bora-dev-data-kamino/
ls /mnt/odin/az-new-legacy-data/
# FSx Filesystem 2 (/mnt/qcs)
ls /mnt/qcs/qcs-bali-dev-ingest/
ls /mnt/qcs/qcs-odin-dev-output/
From data manager:
# Kamino ingress data
ls /mnt/ingest/kamino-automation-ingress/
ls /mnt/ingest/kamino-config-ingress/
Checking File State
Files appear as stubs initially (metadata only). Check if data is cached:
lfs hsm_state /mnt/odin/qcs-training-data/<filename>
Example output:
(0x0000000d) released exists archived, archive_id:1
- released: Data not cached (only metadata stub)
- exists: File exists in filesystem
- archived: Data is in S3
Fetching Data from S3
Data is fetched automatically when accessed. To explicitly pre-fetch:
sudo lfs hsm_restore /mnt/odin/qcs-training-data/<filename>
Or simply read the file:
cat /mnt/odin/qcs-training-data/<filename>
Syncing Data to S3
Files written to FSx are automatically exported to S3. To manually trigger:
Archive (export) to S3:
sudo lfs hsm_archive /mnt/odin/qcs-training-data/<filename>
Release from cache (save space):
sudo lfs hsm_release /mnt/odin/qcs-training-data/<filename>
Check sync status:
lfs hsm_state /mnt/odin/qcs-training-data/<filename>
Auto-Import/Export Behavior
When files are added, changed, or deleted in S3 buckets:
- FSx automatically syncs changes to mount points
- Files appear as stubs (metadata only) initially
- Data is fetched on-demand when accessed
- Changes made in FSx are automatically exported back to S3