Lines Matching refs:dirty
22 dirty data to the backing device is always done sequentially, scanning from the
34 or dirty data), caching is automatically disabled; if dirty data was present
35 in the cache it first disables writeback caching and waits for all dirty data
77 but will allow for mirroring of metadata and dirty data in the future. Your new
104 but all the cached data will be invalidated. If there was dirty data in the
126 - When we detach, we first try to flush any dirty data (if we were running in
128 read some of the dirty data, though.
212 Write to this file to detach from a cache set. If there is dirty data in the
216 Amount of dirty data for this backing device in the cache. Continuously
248 clean: Part of a cache set, and there is no cached dirty data.
250 dirty: Part of a cache set, and there is cached dirty data.
253 dirty data cached but the cache set was unavailable; whatever data was on the
261 When dirty data is written to the cache and it previously did not contain
266 If nonzero, bcache tries to keep around this percentage of the cache dirty by
276 If off, writeback of dirty data will not take place at all. Dirty data will
331 Percentage of cache device which doesn't contain dirty data, and could
340 Amount of dirty data is in the cache (updated when garbage collection runs).
350 reaches io_error_limit dirty data is written out and the cache is disabled.
368 Detaches all backing devices and closes the cache devices; if dirty data is