mirror of
https://github.com/rustfs/rustfs.git
synced 2026-09-23 11:03:26 +00:00
17ddecb075
* fix(ecstore)!: bind bitrot shards to immutable part identities Verify part, coding-index, and block identity across write, GET, and Heal paths. Preserve identities across metadata-only copies and repair, include them in multipart quorum selection, and require payload proof for receipts. Keep legacy decoding with conservative parity and target-digest validation, and document its unsupported cases and additional verification I/O. BREAKING CHANGE: New bound-v1 shards require compatible readers throughout the fleet. Legacy objects without sufficient integrity evidence return an error; binary rollback after new writes requires verified data migration. Refs: rustfs/backlog#2497 * fix(ecstore): preserve shard framing with independent integrity Commit immutable part-generation Merkle roots and replicated proof indexes without changing existing checksum frames. Verify reads, reconstruction and Deep Heal against metadata quorum; keep legacy reads and explicitly defer unproven legacy data repair. Preserve multipart rollback generations, require acknowledged durable index publication, and add decoder compatibility and donor-shard regression coverage. * fix(heal): verify protected partial-write replay
30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
# Documentation
|
|
|
|
Use the focused indexes rather than treating this directory as an unordered
|
|
collection:
|
|
|
|
- [Architecture knowledge base](architecture/README.md)
|
|
- [Testing references](testing/README.md)
|
|
|
|
## Operations
|
|
|
|
Operational runbooks live under [`operations/`](operations/). Replication
|
|
operators should start with:
|
|
|
|
| Runbook | Use it for |
|
|
|---|---|
|
|
| [Site replication operations](operations/site-replication-operations.md) | Health fields, pending operations, outage recovery, re-pair admission, IAM/SSE boundaries, and upgrades. |
|
|
| [Replication target check](operations/replication-check.md) | Validating an S3 destination and version fidelity before enabling replication. |
|
|
| [Replication object size limits](operations/replication-object-size-limits.md) | Multipart routing, large-object limits, and retry characteristics. |
|
|
| [Replication outbound transport](operations/replication-outbound-transport.md) | Integrity headers, generic target behavior, and transport knobs. |
|
|
|
|
Other runbooks remain grouped by filename in [`operations/`](operations/);
|
|
architecture pages link to the relevant runbook where a cross-boundary
|
|
procedure is required.
|
|
|
|
For storage dashboards, see [Storage metrics and observer selection](operations/storage-metrics.md):
|
|
drive ownership, snapshot freshness, counter queries, and rolling upgrades.
|
|
|
|
For optional shard commitments, see [Independent shard integrity rollout](operations/shard-integrity-rollout.md):
|
|
activation, legacy repair results, multipart mode changes, and rollback limits.
|