{
  "slug": "misdirected-write",
  "term": "Misdirected write",
  "aliases": [],
  "definition": "A misdirected write stores an update at the wrong address or on the wrong device.",
  "note": "The original destination may remain stale while another location is overwritten; a valid checksum does not by itself bind returned data to the requested location.",
  "related": [
    "lost-write",
    "protection-information",
    "parity-pollution"
  ],
  "citations": [
    {
      "id": "field",
      "title": "Bairavasundaram et al. An Analysis of Data Corruption in the Storage Stack. FAST 2008, sections 2-3 and 6.",
      "url": "https://www.usenix.org/legacy/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/index.html",
      "accessed": "2026-10-11"
    },
    {
      "id": "hesela-integrity",
      "title": "Hesela: checksum, identity and freshness boundaries with executable synthetic examples",
      "url": "https://hesela.com/analyses/checksums-identity-and-lost-writes/",
      "accessed": "2026-10-11"
    }
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-11"
}