Lines Matching refs:backing

27 dirty data to the backing device is always done sequentially, scanning from the
45 and backing device must be formatted before use::
51 you format your backing devices and cache device at the same time, you won't
62 Registering the backing device makes the bcache device show up in /dev; you can
66 slow devices as bcache backing devices without a cache, and you can choose to add
94 After your cache device and backing device are registered, the backing device
95 must be attached to your cache set to enable caching. Attaching a backing
102 your bcache devices. If a backing device has data in a cache somewhere, the
107 can force run the backing device::
111 (You need to use /sys/block/sdb (or whatever your backing device is called), not
115 The backing device will still use that cache set if it shows up in the future,
126 the backing devices to passthrough mode.
129    backing device.
149 If registering the backing device doesn't help, it's already there, you just need
188 If bcache is not available in the kernel, a filesystem on the backing
190 of the backing device created with --offset 8K, or any value defined by
197 This should present your unmodified backing device data in /dev/loop0
226 start backing device with missing cache::
261 /dev/bcache<N> This will work faster than if you dmcrypt both the backing
269 if there are any active backing or caching devices left on it:
277 2) But if your backing device is gone, this won't work::
289    This causes the backing bcache to be removed from /sys/fs/bcache and
319    The default metadata size in bcache is 8k.  If your backing device is
396 Sysfs - backing device
417   Amount of dirty data for this backing device in the cache. Continuously
445   The backing device can be in one of four different states:
453   inconsistent: The backing device was forcibly run by the user when there was
455   backing device has likely been corrupted.
458   Write to this file to shut down the bcache device and close the backing
481 Sysfs - backing device stats
516   Symlink to each of the attached backing devices.
561   backing devices have been shut down.
567   Detaches all backing devices and closes the cache devices; if dirty data is
595   completed. When this occurs the data is reread from the backing device.