Jump to content
From ArchWiki

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

Reason: Some first-person comments, see Help:Style. (Discuss in Talk:Bcache)

Related articles

- Bcachefs
- Flashcache
- LVM2

Bcache (block cache) allows one to use an SSD as a read/write cache (in writeback mode) or read cache (writethrough or writearound) for another blockdevice (generally a rotating HDD or array). This article will show how to install Arch using Bcache as the root partition. For an intro to bcache itself, see the bcache homepage. Be sure to read and reference the bcache manual.

Tip: An alternative to Bcache is the LVM cache.

Bcache needs the backing device to be formatted as a bcache block device. In most cases, blocks to-bcache can do an in-place conversion.

This article or section is out of date.

Reason: Backwards incompatible changes to on-disk format for Linux 3.18 were reported to be false. bcache on-disk format changes had not landed upstream yet as of 3.19. Since then, Linux is at version 6.2, can the relevant sentence reflect when exactly the breaking changes took place ? Is the mention still needed ? (Discuss in Talk:Bcache)
Warning:

- Be sure you back up any important data first.
- The bcache-dev branch is under heavy development. The on-disk format has undergone changes in 3.18 which are not backwards compatible with previous formats[1]. Note: This only applies to users who compile-in bcache-dev. The version built-in to the upstream Linux kernel is unaffected[2].
- Bcache and btrfs could leave you with a corrupted filesystem. Please visit this post for more information. Btrfs wiki reports that it was fixed in kernels 3.19+ [3].

## Setting up bcached btrfs file systems on an existing system

Warning: make-bcache will not import an existing drive or partition – it will reformat it.

### Preparation

Install bcache-toolsAUR.

Use fdisk to create the appropriate partitions on the SSD's and hard drives to hold the cache and the backing data.

Tip: It is possible to create many partitions on a single drive. This allows for testing of elaborate setups before committing. Be aware all data will be lost when the drive fails. This will also kill performance of the drive, due to unfavorable access patterns.

### Situation: 1 hard drive and 1 read cache SSD

Warning:

- When a single hard drive fails, all data is lost.
- Do not enable write caching, as that can cause data loss when the SSD fails

    +--------------+
    | btrfs /mnt   |
    +--------------+
    | /dev/Bcache0 |
    +--------------+
    | Cache        |
    | /dev/sdk1    |
    +--------------+
    | Data         |
    | /dev/sdv1    |
    +--------------+

1. Format the backing device (This will typically be your mechanical drive). The backing device can be a whole device, a partition or any other standard block device. This will create /dev/bcache0

    # make-bcache -B /dev/sdv1

2. Format the cache device (This will typically be your SSD). The cache device can be a whole device, a partition or any other standard block device

    # make-bcache -C /dev/sdk1

In this example the default block and bucket sizes of 512B and 128kB are used. The block size should match the backing devices sector size which will usually be either 512 or 4k. The bucket size should match the erase block size of the caching device with the intent of reducing write amplification. For example, using a HDD with 4k sectors and an SSD with an erase block size of 2MB this command would look like

    # make-bcache --block 4k --bucket 2M -C /dev/sdk1

Note: You may need to omit the `--block 4k` option, see Cannot attach cache device to backing device.

3. Get the uuid of the cache device

    # bcache-super-show /dev/sdk1 | grep cset
    cset.uuid		f0e01318-f4fd-4fab-abbb-d76d870503ec

4. Register the cache device against your backing device. Replace the example uuid with the uuid of your cache. Udev rules will take care of this on reboot and will only need to be done once.

    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache0/bcache/attach

5. Create the btrfs filesystem.

    # mkfs.btrfs /dev/bcache0

6. mount the filesystem

    # mount /dev/bcache0 /mnt

7. If you want to have this partition available during the initcpio (i.e. you require it at some point in the boot process) you need to add 'bcache' to your modules array in /etc/mkinitcpio.conf as well as adding the 'bcache' hook in your list between block and filesystems. You must then regenerate the initramfs.

### Situation: 4 hard drives and 1 read cache SSD

Warning:

- Do not enable write caching, as that can cause data loss when the SSD fails

    +-----------------------------------------------------------+
    |                         btrfs /mnt                        |
    +--------------+--------------+--------------+--------------+
    | /dev/Bcache0 | /dev/Bcache1 | /dev/Bcache2 | /dev/Bcache3 |
    +--------------+--------------+--------------+--------------+
    |                           Cache                           |
    |                         /dev/sdk1                         |
    +--------------+--------------+--------------+--------------+
    | Data         | Data         | Data         | Data         |
    | /dev/sdv1    | /dev/sdw1    | /dev/sdx1    | /dev/sdy1    |
    +--------------+--------------+--------------+--------------+

1. Format the backing devices (These will typically be your mechanical drives). The backing devices can be whole devices, partitions or any other standard block devices. This will create /dev/bcache0, /dev/bcache1, /dev/bcache2 and /dev/bcache3

    # make-bcache -B /dev/sdv1
    # make-bcache -B /dev/sdw1
    # make-bcache -B /dev/sdx1
    # make-bcache -B /dev/sdy1

2. Format the cache device (This will typically be your SSD). The cache device can be a whole device, a partition or any other standard block device. Only one cache device can be added to a group of backing devices.

    # make-bcache -C /dev/sdk1

3. Get the uuid of the cache device

    # bcache-super-show /dev/sdk1 | grep cset
    cset.uuid		f0e01318-f4fd-4fab-abbb-d76d870503ec

4. Register the cache device against your backing devices. Replace the example uuid with the uuid of your cache.

    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache0/bcache/attach
    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache1/bcache/attach
    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache2/bcache/attach
    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache3/bcache/attach

5. Create the btrfs filesystem. Both the data and the metadata is stored twice in the array, so there will be no data loss when a single hard drive fails. The -L argument defines the label of the filesystem.

    # mkfs.btrfs -L STORAGE -f -d raid1 -m raid1 /dev/bcache0 /dev/bcache1 /dev/bcache2 /dev/bcache3

6. mount the filesystem

    # mount /dev/bcache0 /mnt

### Situation: 3 hard drives and 3 read/write cache SSD's

Warning:

- Each HDD needs its own SSD, to avoid data loss if a SSD in writeback mode fails.

    +--------------------------------------------+
    |                  btrfs /mnt                |
    +--------------+--------------+--------------+
    | /dev/Bcache0 | /dev/Bcache1 | /dev/Bcache2 |
    +--------------+--------------+--------------+
    | Cache        | Cache        | Cache        |
    | /dev/sdk1    | /dev/sdl1    | /dev/sdm1    |
    +--------------+--------------+--------------+
    | Data         | Data         | Data         |
    | /dev/sdv1    | /dev/sdw1    | /dev/sdx1    |
    +--------------+--------------+--------------+

1. Format the backing devices (These will typically be your mechanical drives). The backing devices can be whole devices, partitions or any other standard block devices. This will create /dev/bcache0, /dev/bcache1 and /dev/bcache2.

    # make-bcache -B /dev/sdv1
    # make-bcache -B /dev/sdw1
    # make-bcache -B /dev/sdx1

2. Format the cache devices (This will typically be your SSD's). The cache devices can be whole devices, partitions or any other standard block devices. To avoid data loss in case of a failing SSD, each backing device needs its own SSD if it is in writeback mode. Cache SSD's in writethrough and in writearound mode can be shared by multiple backing devices, as they do not cause data loss when they fail.

    # make-bcache -C /dev/sdk1
    # make-bcache -C /dev/sdl1
    # make-bcache -C /dev/sdm1

3. Get the uuid of the cache devices

    # bcache-super-show /dev/sdk1 | grep cset
    cset.uuid		f0e01318-f4fd-4fab-abbb-d76d870503ec
    # bcache-super-show /dev/sdl1 | grep cset
    cset.uuid		4b05ce02-19f4-4cc6-8ca0-1f765671ceda
    # bcache-super-show /dev/sdm1 | grep cset
    cset.uuid		75ff0598-7624-46f6-bcac-c27a3cf1a09f

4. Register the cache devices against your backing devices. Replace the example uuid's with the uuid's of your caches.

    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache0/bcache/attach
    # echo 4b05ce02-19f4-4cc6-8ca0-1f765671ceda > /sys/block/bcache1/bcache/attach
    # echo 75ff0598-7624-46f6-bcac-c27a3cf1a09f > /sys/block/bcache2/bcache/attach

5. enable writeback mode

Warning:

- Bcache write caching can cause a catastrophic failure of a btrfs filesystem.
- Btrfs assumes the underlying device executes writes in order, but bcache writeback may violate that assumption, causing the btrfs filesystem using it to collapse.
- Every layer or write caching adds more risk of losing data in the event of a power loss.
- Use bcache in writeback mode with btrfs at your own risk.

    # echo writeback > /sys/block/bcache0/bcache/cache_mode
    # echo writeback > /sys/block/bcache1/bcache/cache_mode
    # echo writeback > /sys/block/bcache2/bcache/cache_mode

6. Create the btrfs filesystem. Both the data and the metadata is stored twice in the array, so there will be no data loss when a single hard drive fails. The -L argument defines the label of the filesystem.

    # mkfs.btrfs -L STORAGE -f -d raid1 -m raid1 /dev/bcache0 /dev/bcache1 /dev/bcache2

7. mount the filesystem

    # mount /dev/bcache0 /mnt

### Situation: 5 hard drives and 3 cache SSD's

Warning:

- Each cache device in writeback mode must only be used to cache a single backing drive, to avoid data loss if that SSD fails. Writethrough and writearound SSD's can be shared.

    +--------------------------------------------------------------------------+
    |                                btrfs /mnt                                |
    +--------------+--------------+--------------+--------------+--------------+
    | /dev/Bcache0 | /dev/Bcache1 | /dev/Bcache2 | /dev/Bcache3 | /dev/Bcache4 |
    +--------------+--------------+--------------+--------------+--------------+
    | WriteB Cache |     Writethrough or writearound Cache      | WriteB Cache |
    | /dev/sdk1    |                 /dev/sdl1                  | /dev/sdm1    |
    +--------------+--------------+--------------+--------------+--------------+
    | Data         | Data         | Data         | Data         | Data         |
    | /dev/sdv1    | /dev/sdw1    | /dev/sdx1    | /dev/sdy1    | /dev/sdz1    |
    +--------------+--------------+--------------+--------------+--------------+

1. Format the backing devices (These will typically be your mechanical drives). The backing devices can be whole devices, partitions or any other standard block devices. This will create /dev/bcache0, /dev/bcache1, /dev/bcache2, /dev/bcache3 and /dev/bcache4.

    # make-bcache -B /dev/sdv1
    # make-bcache -B /dev/sdw1
    # make-bcache -B /dev/sdx1
    # make-bcache -B /dev/sdy1
    # make-bcache -B /dev/sdz1

2. Format the cache devices (This will typically be your SSD's). The cache devices can be whole devices, partitions or any other standard block devices. To avoid data loss in case of a failing SSD, each backing device needs its own SSD if it is in writeback mode. Cache SSD's in writethrough and in writearound mode can be shared by multiple backing devices, as they do not cause data loss when they fail.

    # make-bcache -C /dev/sdk1
    # make-bcache -C /dev/sdl1
    # make-bcache -C /dev/sdm1

3. Get the uuid of the cache devices

    # bcache-super-show /dev/sdk1 | grep cset
    cset.uuid		f0e01318-f4fd-4fab-abbb-d76d870503ec
    # bcache-super-show /dev/sdl1 | grep cset
    cset.uuid		4b05ce02-19f4-4cc6-8ca0-1f765671ceda
    # bcache-super-show /dev/sdm1 | grep cset
    cset.uuid		75ff0598-7624-46f6-bcac-c27a3cf1a09f

4. Register the cache devices against your backing devices. Replace the example uuid's with the uuid's of your caches.

    # echo f0e01318-f4fd-4fab-abbb-d76d870503ec > /sys/block/bcache0/bcache/attach
    # echo 4b05ce02-19f4-4cc6-8ca0-1f765671ceda > /sys/block/bcache1/bcache/attach
    # echo 4b05ce02-19f4-4cc6-8ca0-1f765671ceda > /sys/block/bcache2/bcache/attach
    # echo 4b05ce02-19f4-4cc6-8ca0-1f765671ceda > /sys/block/bcache3/bcache/attach
    # echo 75ff0598-7624-46f6-bcac-c27a3cf1a09f > /sys/block/bcache4/bcache/attach

5. enable writeback mode on non-shared caches

    # echo writeback > /sys/block/bcache0/bcache/cache_mode
    # echo writeback > /sys/block/bcache4/bcache/cache_mode

6. Create the btrfs filesystem. Both the data and the metadata is stored twice in the array, so there will be no data loss when a single hard drive fails. The -L argument defines the label of the filesystem.

    # mkfs.btrfs -L STORAGE -f -d raid1 -m raid1 /dev/bcache0 /dev/bcache1 /dev/bcache2 /dev/bcache3 /dev/bcache4

7. mount the filesystem

    # mount /dev/bcache0 /mnt

### Bcache management

1. Check that everything has been correctly setup

    # cat /sys/block/bcache0/bcache/state

The output can be:

- `no cache`: this means you have not attached a caching device to your backing bcache device
- clean: this means everything is ok. The cache is clean.
- dirty: this means everything is setup fine and that you have enabled writeback and that the cache is dirty.
- inconsistent: you are in trouble because the backing device is not in sync with the caching device

You can have a `/dev/bcache0` device associated with a backing device with no caching device attached. This means that all I/O (read/write) are passed directly to the backing device (pass-through mode)

2. See what caching mode is in use

    # cat /sys/block/bcache0/bcache/cache_mode

    [writethrough] writeback writearound none

In the above example, the writethrough mode is enabled.

3. Show info about a bcached device:

    # bcache-super-show /dev/sdXY

4. Stop the backing device:

    # echo 1 > /sys/block/sdX/sdX[Y]/bcache/stop

5. Detach a caching device:

    # echo 1 > /sys/block/sdX/sdX[Y]/bcache/detach

6. Safely remove the cache device

    # echo cache-set-uuid > /sys/block/bcache0/bcache/detach

7. Release attached devices

    # echo 1 > /sys/fs/bcache/cache-set-uuid/stop

## Installation to a bcache device

1. Boot on the install disk (2013.08.01 minimum).

2. Install the bcache-toolsAUR.

3. Partition your HDD

Note: While it may be true that Grub2 does not offer support for bcache as noted below, it does, however, fully support UEFI. It follows then, that so long as the necessary modules for the linux kernel to properly handle your boot device are either compiled into the kernel or are included in an initramfs, and you can include these files on it, the separate boot partition described below may be omitted in favor of the FAT EFI system partition. See GRUB and/or UEFI for more.

grub cannot handle bcache, so you will need at least 2 partitions (boot and one for the bcache backing device). If you are doing UEFI, you will need an EFI system partition (ESP) as well. E.g.:

         1            2048           22527   10.0 MiB    EF00  EFI System
         2           22528          432127   200.0 MiB   8300  arch_boot
         3          432128       625142414   297.9 GiB   8300  bcache_backing

Note: This example has no swapfile/partition. For a swap partition on the cache, use LVM in step 7. For a swap partition outside the cache, be sure to make a swap partition now.

4. Configure your HDD as a bcache backing device.

    # make-bcache -B /dev/sda3

Note:

- When preparing any boot disk it is important to know the ramifications of any decision you may make. Please review and review again the documentation for your chosen boot-loader/-manager and consider seriously how it might relate to bcache.
- If all associated disks are partitioned at once as below bcache will automatically attach "-B backing stores" to the "-C ssd cache" and step 5 is unnecessary.

    # make-bcache -B /dev/sd? /dev/sd? -C /dev/sd?

You now have a `/dev/bcache0` device.

5. Configure your SSD

Format the SSD as a caching device and link it to the backing device

    # make-bcache -C /dev/sdb
    # echo /dev/sdb > /sys/fs/bcache/register
    # echo UUID__from_previous_command > /sys/block/bcache0/bcache/attach

Note: If the UUID is forgotten, it can be found with `ls /sys/fs/bcache/` after the cache device has been registered.

6. Format the bcache device. Use LVM or btrfs subvolumes if you want to divide up the `/dev/bcache0` device how you like (ex for separate `/`, `/home`, `/var`, etc):

    # mkfs.btrfs /dev/bcache0
    # mount /dev/bcache0 /mnt/
    # btrfs subvolume create /mnt/root
    # btrfs subvolume create /mnt/home
    # umount /mnt

You can even setup LUKS on it if you want using e.g. cryptsetup. Referencing the bcache device in the 'cryptdevice' kernel option will work fine, for instance.

7. Prepare the installation mount point:

    # mkfs.ext4 /dev/sda2
    # mkfs.msdos /dev/sda1 (if your ESP is at least 500MB, use mkfs.vfat to make a FAT32 partition instead)

Now install arch-install-scripts package. Then:

    # mount /dev/bcache0 -o subvol=root,compress=lzo /mnt/
    # mount --mkdir /dev/bcache0 -o subvol=home,compress=lzo /mnt/home
    # mount --mkdir /dev/sda2 /mnt/boot
    # mount --mkdir /dev/sda1 /mnt/efi

8. Install the system as per the Installation guide as normal except this:

Before you edit `/etc/mkinitcpio.conf` and run `mkinitcpio -p linux`:

- Install bcache-toolsAUR.
- Edit `/etc/mkinitcpio.conf`:
  - add the "bcache" module
  - add the "bcache" hook between block and filesystem hooks

Note: Should you want to open the backing device from the installation media for any reason after a reboot you must register it manually. Make sure the bcache module is loaded and then echo the relevant devices to /sys/bcache/register. You should see whether this worked or not by using dmesg.

## Accessing from the install disk

This is how to access a bcache partition from the install disk that was present before the install disk was booted. Boot the install disk and install bcache-toolsAUR from the AUR, just as in the previous section. Then, add the module to the kernel:

    # modprobe bcache

Your device will not appear immediately at `/dev/bcache*`. To force the kernel to find it, tell it to reread the partition table:

    # partprobe

Now, `/dev/bcache*` should be present, and you can carry on mounting, reformatting, etc. from here.

To start the cache without having to configure the internet and install bcache-toolsAUR, load the kernel module just as before—it is included in the mainline kernel. Then start the cache by registering all of the slave devices:

    # echo /dev/sdX > /sys/fs/bcache/register
    # echo /dev/sdY > /sys/fs/bcache/register
    # ...

The bcache device will appear right after the last required slave device is registered.

A writethrough backing device can be started without having to register any caches. This can be done if there are a lot of them and you are in a hurry, or if some of the caches are inaccessible for some reason. Register the device, as above, then start it:

    # echo 1 > /sys/block/sdX/bcache/running

Bcache has not actually detached any caches, and will still add any cache devices if they are registered. This command will "work" on writeback backing devices, but there will be massive data corruption. Only do this if the missing cache is totally unrecoverable.

## Configuring

Warning: Do not enable the `discard` option! It can cause unrecoverable corruption. [4][5]

There are many options that can be configured (such as cache mode, cache flush interval, sequential write heuristic, etc.) This is currently done by writing to files in `/sys`. See the bcache user documentation.

Changing the cache mode is done by echoing one of `writethrough`, `writeback`, `writearound` or `none` to `/sys/block/bcache[0-9]/bcache/cache_mode`.

Note that some changes to `/sys` are temporary, and will revert back after a reboot (It seems that at least cache_mode does not need this workaround). To set custom configurations at boot create a .conf file in `/etc/tmpfiles.d`. To set, in a persistent fashion, the sequential cutoff for `bcache0` to 1 MB and write back you could create a file `/etc/tmpfiles.d/my-bcache.conf` with the contents:

    w /sys/block/bcache0/bcache/sequential_cutoff - - - - 1M
    w /sys/block/bcache0/bcache/cache_mode        - - - - writeback

## Advanced operations

### Resize backing device

It is possible to resize the backing device so long as you do not move the partition start. This process is described in the mailing list. Here is an example using btrfs volume directly on bcache0. For LVM containers or for other filesystems, procedure will differ.

#### Example of growing

In this example, I grow the filesystem by 4GB.

1. Reboot to a live CD/USB Drive (need not be bcache enabled) and use fdisk, gdisk, parted, or your other favorite tool to delete the backing partition and recreate it with the same start and a total size 4G larger.

Warning: Do not use a tool like GParted that might perform filesystem operations! It will not recognize the bcache partition and might overwrite part of it!!

2. Reboot to your normal install. Your filesystem will be currently mounted. That is fine. Issue the command to resize the partition to its maximum. For btrfs, that is

    # btrfs filesystem resize max /

For ext3/4, that is:

    # resize2fs /dev/bcache0

#### Example of shrinking

In this example, I shrink the filesystem by 4GB.

1. Disable writeback cache (switch to writethrough cache) and wait for the disk to flush.

    # echo writethrough > /sys/block/bcache0/bcache/cache_mode
    $ watch cat /sys/block/bcache0/bcache/state

wait until state reports "clean". This might take a while.

##### Force flush of cache to backing device

I suggest to use

     # echo 0 > /sys/block/bcache0/bcache/writeback_percent

This will flush the dirty data of the cache to the backing device in less a minute.

Revert back the value after with

    # echo 10 > /sys/block/bcache0/bcache/writeback_percent

2. Shrink the mounted filesystem by something more than the desired amount, to ensure we do not accidentally clip it later. For btrfs, that is:

    # btrfs filesystem resize -5G /

For ext3/4 you can use resize2fs, but only if the partition is unmounted

    $ df -h /home

    /dev/bcache0    290G   20G   270G   1% /home

    # umount /home
    # resize2fs /dev/bcache0 283G

3. Reboot to a LiveCD/USB drive (does not need to support bcache) and use fdisk, gdisk, parted, or your other favorite tool to delete the backing partition and recreate it with the same start and a total size 4G smaller.

Warning: Do not use a tool like GParted that might perform filesystem operations! It will not recognize the bcache partition and might overwrite part of it!!

4. Reboot to your normal install. Your filesystem will be currently mounted. That is fine. Issue the command to resize the partition to its maximum (that is, the size we shrunk the actual partition to in step 3). For btrfs, that is:

    # btrfs filesystem resize max /

For ext3/4, that is:

    # resize2fs /dev/bcache0

5. Re-enable writeback cache if you want that enabled:

    # echo writeback > /sys/block/bcache0/bcache/cache_mode

Note: If you are very careful you can shrink the filesystem to the exact size in step 2 and avoid step 4. Be careful, though, many partition tools do not do exactly what you want, but instead adjust the requested partition start/end points to end on sector boundaries. This may be difficult to calculate ahead of time

## Troubleshooting

### /dev/bcache device does not exist on bootup

If you are sent to a busy box shell with an error:

    ERROR: Unable to find root device 'UUID=b6b2d82b-f87e-44d5-bbc5-c51dd7aace15'.
    You are being dropped to a recovery shell
        Type 'exit' to try and continue booting

This might happen if the backing device is configured for "writeback" mode (default is writearound). When in "writeback" mode, the /dev/bcache0 device is not started until the cache device is both registered and attached. Registering is something that needs to happen every bootup, but attaching should only have to be done once.

To continue booting, try one of the following:

- Register both the backing device and the caching device

    # echo /dev/sda3 > /sys/fs/bcache/register
    # echo /dev/sdb > /sys/fs/bcache/register

If the /dev/bcache0 device now exists, type exit and continue booting. You will need to fix your initcpio to ensure devices are registered before mounting the root device.

Note:

- An error of "sh: echo: write error: Invalid argument" means the device was already registered or is not recognized as either a bcache backing device or cache. If using the udev rule on boot it should only attempt to register a device if it finds a bcache superblock
- This can also happen if using udev's 69-bcache.rules in Installation's step 7 and blkid and bcache-probe "disagree" due to rogue superblocks. See bcache's wiki for a possible explanation/resolution.

- Re-attach the cache to the backing device:

If the cache device was registered, a folder with the UUID of the cache should exist in `/sys/fs/bcache`. Use that UUID when following the example below:

    # ls /sys/fs/bcache/

    b6b2d82b-f87e-44d5-bbc5-c51dd7aace15     register     register_quiet

    # echo b6b2d82b-f87e-44d5-bbc5-c51dd7aace15 > /sys/block/sda/sda3/bcache/attach

If the `/dev/bcache0` device now exists, type exit and continue booting. You should not have to do this again. If it persists, ask on the bcache mailing list.

Note: An error of `sh: echo: write error: Invalid argument` means the device was already attached. An error of `sh: echo: write error: No such file or directory` means the UUID is not a valid cache (make sure you typed it correctly).

- Invalidate the cache and force the backing device to run without it. You might want to check some stats, such as "dirty_data" so you have some idea of how much data will be lost.

    # cat /sys/block/sda/sda3/bcache/dirty_data

    -3.9M

dirty data is data in the cache that has not been written to the backing device. If you force the backing device to run, this data will be lost, even if you later re-attach the cache.

    # cat /sys/block/sda/sda3/bcache/running

    0

    # echo 1 > /sys/block/sda/sda3/bcache/running

The `/dev/bcache0` device will now exist. Type exit and continue booting. You might want to unregister the cache device and run make-bcache again. An fsck on `/dev/bcache0` would also be wise. See the bcache documentation.

Warning: Only invalidate the cache if one of the two options above did not work.

### /sys/fs/bcache/ does not exist

The kernel you booted is not bcache enabled, or you the bcache module is not loaded

### write error: Invalid argument when trying to attach a device due to mismatched block parameter

Given `bash: echo: write error: Invalid argument` when trying to attach a device, and the actual error is shown with dmesg:

    bcache: bch_cached_dev_attach() Couldn't attach sdc: block size less than set's block size

This happens because the `--block 4k` parameter was not set on either device and defaults can mismatch.

Creating both the backing and caching device in one command automatically solves the issue, but when using separate commands the block size parameter sometimes needs to be set manually on both devices.

### Device or resource busy

When a device is in use as a bcache backing device, it can not be formatted nor partitioned:

    # make-bcache -C /dev/sdb1
    Can't open dev /dev/sdb1: Device or resource busy

    # fdisk /dev/sdb

    Welcome to fdisk (util-linux 2.37.2).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.

    This disk is currently in use - repartitioning is probably a bad idea.
    It's recommended to umount all file systems, and swapoff all swap
    partitions on this disk.

    Command (m for help): q

To fix this, first run this command to confirm the disk is actually used as a bcache backing device:

    # bcache-super-show /dev/sdb1
    sb.magic		ok
    sb.first_sector		8 [match]
    sb.csum			A3D2B8610F6C5E35 [match]
    sb.version		1 [backing device]

    dev.label		(empty)
    dev.uuid		5a868788-65a2-4564-b4b7-c1817d0b6080
    dev.sectors_per_block	1
    dev.sectors_per_bucket	1024
    dev.data.first_sector	16
    dev.data.cache_mode	1 [writeback]
    dev.data.cache_state	2 [dirty]

    cset.uuid		42dcb651-6b53-4b65-bc49-9b1ca0acc5b1

Then stop the backing device. This will also remove the corresponding /dev/bcache device.

    # echo 1 > /sys/class/block/sdb1/bcache/stop

    # dmesg
    [ 3171.263577] bcache: bcache_device_free() bcache0 stopped

Now the device can be partitioned:

    # fdisk /dev/sdb

    Welcome to fdisk (util-linux 2.37.2).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.

    Command (m for help): q

When fdisk exits, the kernel scans the drive again, notices it's a bcache backing device, and uses the drive as a backing device.

    # dmesg
    [ 3190.643270]  sdb: sdb1
    [ 3190.833029] bcache: register_bdev() registered backing device sdb1

This creates the directory bcache under /sys/class/block/sdb1/

    # ls /sys/class/block/sdb1/
    alignment_offset  bcache  dev  discard_alignment  holders  inflight  partition	power  ro  size  start	stat  subsystem  uevent

## See also

- Bcache Homepage
- Bcache Manual

Category:

- File systems

Hidden categories:

- Pages or sections flagged with Template:Style
- Pages or sections flagged with Template:Out of date