Lines Matching refs:backing
30 dirty data to the backing device is always done sequentially, scanning from the
48 and backing device must be formatted before use::
54 you format your backing devices and cache device at the same time, you won't
69 Registering the backing device makes the bcache device show up in /dev; you can
73 slow devices as bcache backing devices without a cache, and you can choose to add
101 After your cache device and backing device are registered, the backing device
102 must be attached to your cache set to enable caching. Attaching a backing
109 your bcache devices. If a backing device has data in a cache somewhere, the
114 can force run the backing device::
118 (You need to use /sys/block/sdb (or whatever your backing device is called), not
122 The backing device will still use that cache set if it shows up in the future,
133 the backing devices to passthrough mode.
136 backing device.
156 If registering the backing device doesn't help, it's already there, you just need
195 If bcache is not available in the kernel, a filesystem on the backing
197 of the backing device created with --offset 8K, or any value defined by
204 This should present your unmodified backing device data in /dev/loop0
233 start backing device with missing cache::
268 /dev/bcache<N> This will work faster than if you dmcrypt both the backing
276 if there are any active backing or caching devices left on it:
284 2) But if your backing device is gone, this won't work::
296 This causes the backing bcache to be removed from /sys/fs/bcache and
326 The default metadata size in bcache is 8k. If your backing device is
403 Sysfs - backing device
424 Amount of dirty data for this backing device in the cache. Continuously
452 The backing device can be in one of four different states:
460 inconsistent: The backing device was forcibly run by the user when there was
462 backing device has likely been corrupted.
465 Write to this file to shut down the bcache device and close the backing
488 Sysfs - backing device stats
523 Symlink to each of the attached backing devices.
568 backing devices have been shut down.
574 Detaches all backing devices and closes the cache devices; if dirty data is
602 completed. When this occurs the data is reread from the backing device.