Lines Matching refs:backing
22 dirty data to the backing device is always done sequentially, scanning from the
40 and backing device must be formatted before use.
45 you format your backing devices and cache device at the same time, you won't
55 Registering the backing device makes the bcache device show up in /dev; you can
82 After your cache device and backing device are registered, the backing device
83 must be attached to your cache set to enable caching. Attaching a backing
90 your bcache devices. If a backing device has data in a cache somewhere, the
95 can force run the backing device:
99 (You need to use /sys/block/sdb (or whatever your backing device is called), not
103 The backing device will still use that cache set if it shows up in the future,
113 the backing devices to passthrough mode.
116 backing device.
216 Amount of dirty data for this backing device in the cache. Continuously
244 The backing device can be in one of four different states:
252 inconsistent: The backing device was forcibly run by the user when there was
254 backing device has likely been corrupted.
257 Write to this file to shut down the bcache device and close the backing
316 Symlink to each of the attached backing devices.
362 backing devices have been shut down.
368 Detaches all backing devices and closes the cache devices; if dirty data is
395 completed. When this occurs the data is reread from the backing device.