libra cache

Inspect Libra's tiered-storage / LRU cache configuration (lore.md §0.10). This is a diagnostic helper that surfaces the existing LIBRA_STORAGE_* tunables so you can confirm what the running storage backend would apply.

Synopsis

libra cache info

Description

cache info reports the resolved storage/cache tunables, in the same way the tiered storage backend resolves them (environment first, then the global config DB), so the reported values match what the backend uses:

• storage — the raw LIBRA_STORAGE_TYPE value (local only when unset; otherwise your exact value, e.g. s3 / r2 — a wrong-case R2 is shown verbatim and reports non-tiered).
• tier — whether the config selects a durable tier: LIBRA_STORAGE_TYPE is a case-sensitive s3 / r2 that also passes every static check the backend applies before connecting (non-empty bucket, parseable LIBRA_STORAGE_ENDPOINT, non-empty LIBRA_STORAGE_ACCESS_KEY / LIBRA_STORAGE_SECRET_KEY). So a wrong-case R2, an empty key, or a malformed endpoint reports non-tiered rather than misleading you. The cache tunables only take effect when tiered; a local-only repository caches nothing. An actual connection additionally needs valid credentials, which this static report does not validate.
• threshold — the small/large object threshold in bytes (LIBRA_STORAGE_THRESHOLD, default 1 MiB). Objects at or above this size are LRU-cached rather than stored permanently.
• cache — the local LRU disk budget in bytes (LIBRA_STORAGE_CACHE_SIZE, default 200 MiB) for large cached objects.

An unparseable numeric value falls back to the default (mirroring the storage backend's lenient parse), so cache info never fails on a bad value. It needs no repository.

Storage / cache environment variables

Options

Exit codes

cache evict (lore.md 2.9)

Evicts verified-durable large loose objects (>= the tiered threshold) from the local cache, oldest-first by materialization time, until under the configured budget (LIBRA_STORAGE_CACHE_SIZE, overridable with --max-size; --max-size 0 evicts every verified candidate). Safety: each unlink is gated on an error-aware durability probe run immediately before it — an object the durable tier confirms absent is skipped (push/backup to make it durable), a probe error is never treated as absence, and three leading probe failures abort the run with nothing deleted. --dry-run reports the outcome (probes still run); --min-age (default 600s) skips freshly materialized objects. Reads of evicted objects self-heal transparently from the durable tier (re-verified, re-cached) — but are unavailable offline. Local-only repositories have nothing evictable; the offline read policy refuses (probes impossible). Background use: libra maintenance run --task cache-evict (not in the default task set). Residual risk (documented): presence is not integrity — a corrupt remote copy would leave no good copy; v1 relies on S3/R2 server-side integrity.

Examples

# Show the resolved storage/cache tunables with the current environment.
libra cache info

# Inspect a tiered (R2) configuration with a custom LRU budget.
LIBRA_STORAGE_TYPE=r2 LIBRA_STORAGE_CACHE_SIZE=536870912 libra cache info

# Structured output for tooling.
libra --json cache info

Comparison with Git

Git has no equivalent; this is a Libra diagnostic extension for its tiered object store, classified intentionally-different in COMPATIBILITY.md.