{
  "slug": "storage-resource-domain",
  "term": "Storage resource domain",
  "aliases": [
    "storage resource constraint domain"
  ],
  "definition": "A storage resource domain is a set of devices sharing a constrained resource whose budget limits which devices can operate concurrently.",
  "note": "Power, cooling and bandwidth domains need not coincide with failure domains. Pelican distinguishes hard resource limits from performance limits. [pelican]\n\nThe linked six-drive example demonstrates a global budget admitting a locally incompatible set. It enumerates every subset and separately checks active and spinning-up occupancy. The counts describe an invented topology, not observed equipment or a probability of failure. [hesela-model]",
  "status": "shipping",
  "advantages": [],
  "limitations": [
    {
      "text": "Satisfying modeled domain limits alone does not establish hardware safety, failure independence or a recovery-time guarantee.",
      "citationIds": [
        "hesela-model"
      ]
    }
  ],
  "related": [
    "cold-archive",
    "hot-warm-cold",
    "failure-domain",
    "io-scheduler"
  ],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "citations": [
    {
      "id": "pelican",
      "title": "Balakrishnan et al., Pelican, OSDI 2014, sections 2.1-2.2.1, pp. 353-354",
      "url": "https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-balakrishnan.pdf",
      "accessed": "2026-10-23"
    },
    {
      "id": "hesela-model",
      "title": "Hesela: six-drive resource-domain worked example and deterministic results",
      "url": "https://hesela.dev/research/resource-domains/results.json",
      "accessed": "2026-10-23"
    }
  ],
  "updated": "2026-10-23",
  "provenance": [
    "Source review plus an explicitly synthetic example; no execution of the original scheduler or hardware experiment."
  ]
}