Lines Matching +full:cache +full:- +full:block +full:- +full:size

2 dm-era
8 dm-era is a target that behaves similar to the linear target.  In
11 maintains the current era as a monotonically increasing 32-bit
15 partially invalidating the contents of a cache to restore cache
21 era <metadata dev> <origin dev> <block size>
26  block size       block size of origin data device, granularity that is
36 ----------
43 ------------------
48 ------------------
55 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
56 <current era> <held metadata root | '-'>
59 metadata block size	  Fixed block size for each metadata block in
66 			  access. '-' indicates there is no held root
72 The scenario of invalidating a cache when rolling back a vendor
76 ------------------------
78 - Send a checkpoint message to the era target
79 - Make a note of the current era in its status line
80 - Take vendor snapshot (the era and snapshot should be forever
84 ----------------------------------
86 - Cache enters passthrough mode (see: dm-cache's docs in cache.txt)
87 - Rollback vendor storage
88 - Take metadata snapshot
89 - Ascertain which blocks have been written since the snapshot was taken
90   by checking each block's era
91 - Invalidate those blocks in the caching software
92 - Cache returns to writeback/writethrough mode
107 block is performed.  As such dm-era should not be effected by a hard
114 thin-provisioning-tools project:
116     https://github.com/jthornber/thin-provisioning-tools