lustre-hsm · shipping · also Lustre hierarchical storage management

Lustre HSM

Lustre HSM coordinates file-data archival, release and restoration between a Lustre filesystem and an external storage backend.

Related Observatory article: Lustre HSM on hesela.com

Per-file flags describe different properties, not one mutually exclusive label. EXISTS records a backend copy; DIRTY marks divergence. ARCHIVED can coexist with DIRTY: the command manual itself shows that combination. Read the full flagset before inferring that a copy is current. [1] [2]

A successful archive-completion report records the supplied data version, sets ARCHIVED and clears DIRTY and LOST. A state query returns stored metadata without fetching backend payloads. Neither operation is an independent byte-level restore check. [3] [2]

Relations

related
Lustre HSM release, Cold archive tier, Backup, Restore test

Citations

  1. Lustre v2_17_0: lfs-hsm(1), state flags and dirty+archived example (accessed 2026-11-04)
  2. Lustre v2_17_0: mdt_hsm_state_get and mdt_hsm_state_set (accessed 2026-11-04)
  3. Lustre v2_17_0: archive completion and restore/remove compatibility checks (accessed 2026-11-04)
Sources & caveats
  • Pinned Lustre v2_17_0 source review, commit 4b0407a48e9e5b7f17877e8868080e9f40c238c6; no running-cluster or backend recovery test.
  • Replayable source ledger and isolated flag-helper check: https://hesela.dev/research/lustre-hsm/README.md

JSON: /data/terms/lustre-hsm.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Lustre HSM. Hesela. 2026-11-04. https://hesela.dev/terms/lustre-hsm/