GogetaFS
GogetaFS is a research deduplicating file-system design that combines block fingerprints with logical-to-physical mappings to reduce separate metadata persistence.
An LFP entry joins a logical address, fingerprint and physical location; a rebuildable global table supplies fingerprint lookup. Filesystem recovery reconstructs that table. [1]
The pinned SSD implementation compares candidate bytes before sharing a block. A matching fingerprint with unequal content takes the allocation path instead; hash equality alone is not byte equality. The accelerated path also compares hinted content. [2]
Evaluation: Persistent-memory results and FEMU-emulated SSD results have different hardware scopes. The default evaluation disables metadata protection. Faster failure recovery than another deduplicating system does not mean faster normal recovery or faster recovery than the base filesystem. [1]
The paper reports about p = 0.20 over ten runs for its feature-overhead comparison. [1] Failure to reject a difference does not establish performance equivalence; an acceptable effect-size margin and uncertainty assessment are separate requirements. [3]
Relations
Citations
- Pan et al. Don't Maintain Twice, It's Alright: Merged Metadata Management in Deduplication File System with GogetaFS. FAST 2025, sections 4-6.
- GogetaFS SSD source: candidate comparison and hint checks, commit ed330e7c.
- American Statistical Association: Statement on Statistical Significance and P-Values (2016).
- GogetaFS artifact evaluation: prerequisites, experiments and branch mapping.
Further reading
- USENIX FAST 2025: GogetaFS publication record.
- Hesela: deduplication metadata and recovery trade-offs.
Sources & caveats
- Full paper sections 4.2-4.7, 5.2, 6.1-6.7 and artifact appendix inspected. This is source review, not a native implementation benchmark or reproduction. [1]
- The artifact requires a modified kernel and persistent-memory hardware; its scripts can install software and access a configured pmem device. No artifact installation or device experiment was run. [4]
- Code inspection is limited to the pinned candidate-comparison and hint paths; it is not a concurrency, crash-safety or error-propagation audit. [2]