{
  "slug": "parity-inconsistency",
  "term": "Parity inconsistency",
  "aliases": [],
  "definition": "A parity inconsistency is a disagreement between stored parity and parity recomputed from the associated data blocks.",
  "note": "The field study uses this class when individual block checksums pass but parity disagrees during a scrub. [field]\n\nA mismatch does not by itself identify the faulty member. Recomputing parity from unvalidated data can instead create parity pollution, where incorrect data and parity agree. [parity]",
  "related": [
    "parity-pollution",
    "identity-discrepancy",
    "data-scrubbing",
    "raid-5"
  ],
  "citations": [
    {
      "id": "field",
      "title": "Bairavasundaram et al., An Analysis of Data Corruption in the Storage Stack, FAST 2008, sections 2.2-2.3.",
      "url": "https://www.usenix.org/legacy/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram.pdf",
      "accessed": "2026-10-18"
    },
    {
      "id": "parity",
      "title": "Krioukov et al., Parity Lost and Parity Regained, FAST 2008, sections 4.2-4.6.",
      "url": "https://www.usenix.org/legacy/event/fast08/tech/full_papers/krioukov/krioukov_html/main.html",
      "accessed": "2026-10-18"
    },
    {
      "id": "hesela",
      "title": "Hesela: interpreting the historical field study of silent corruption",
      "url": "https://hesela.com/analyses/silent-corruption-checksum-mismatches/",
      "accessed": "2026-10-18"
    }
  ],
  "provenance": [
    "Historical mechanism terminology; not a claim about every modern filesystem's scrub implementation."
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-18"
}