Journal revoke record
A journal revoke record identifies a block whose older journaled images must not be replayed over newer uses of that block.
JBD2 tracks the latest revoking transaction per block; subsequent transaction images can still replay. [1] The concept is not secure erasure or permanent invalidation. The linked model illustrates the distinction with already committed records. [2]
Relations
- related
- crash-consistency, journal-checkpoint, ext4-fast-commit
Limitations
- The cited Linux v6.12 mechanism and explanatory model do not certify a deployed kernel or storage stack. [2]