{
  "slug": "nfs-lookup-cache",
  "term": "NFS lookup cache",
  "aliases": [
    "NFS name cache",
    "NFS dentry cache"
  ],
  "definition": "An NFS lookup cache retains directory-name resolution results, including found and missing entries, subject to revalidation.",
  "note": "Linux lookupcache=positive revalidates negative entries; lookupcache=none revalidates both positive and negative entries before use. These controls do not disable file-data caching. More validation can increase server work.",
  "related": [
    "nfs-storage",
    "nfs-attribute-cache",
    "close-to-open-consistency"
  ],
  "limitations": [
    {
      "text": "Name visibility is not evidence of durable file contents or a multi-file transaction.",
      "citationIds": [
        "rfc7530",
        "hesela-stability"
      ]
    }
  ],
  "citations": [
    {
      "id": "nfs-client",
      "title": "nfs-utils nfs(5), Debian trixie: lookupcache option.",
      "url": "https://manpages.debian.org/trixie/nfs-common/nfs.5.en.html",
      "accessed": "2026-10-14"
    },
    {
      "id": "rfc7530",
      "title": "RFC 7530, section 10.8: Name Caching.",
      "url": "https://datatracker.ietf.org/doc/html/rfc7530#section-10.8",
      "accessed": "2026-10-14"
    },
    {
      "id": "hesela-stability",
      "title": "NFS stable writes: what COMMIT, flush and FUA actually promise",
      "url": "https://hesela.com/analyses/nfs-stable-writes-flush-fua/",
      "accessed": "2026-10-14"
    }
  ],
  "status": "shipping",
  "advantages": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-14"
}