Rolffokkens (talk | contribs) No edit summary |
Rolffokkens (talk | contribs) No edit summary |
||
Line 63: | Line 63: | ||
|results= | |results= | ||
# All steps complete without errors | # All steps complete without errors | ||
|optional= | |||
The original /home partition is no longer used, so we can reclaim its disk space by adding it to the volume group: | |||
# First wipe all metadata: <code>wipefs -a /dev/sda2</code> | |||
# Make /dev/sda2 a bcache backing device: <code>make-bcache -B /dev/sda2</code> | |||
# Note the fact that a new /dev/bcache1 device is created | |||
# Retrieve the cset.uuid from your /dev/sdb1 caching device: <code>bcache-super-show /dev/sdb1</code> | |||
# Attach /dev/sdb1 also to /dev/bcache1: <code>echo <cset.uuid> > /sys/block/bcache1/bcache/attach</code> | |||
There are two bcache devices now: /dev/bcache0 and /dev/bcache1 both using /dev/sdb1 as a caching device. The numbering of the bcache devices happens dynamically during boot, but until you reboot you can safely assume /dev/bcache0 uses /dev/sda4 as a backing device and /dev/bcache1 uses /dev/sda2 as a back device. | |||
# use "bcache-status -s" to see details about your bcache devices. | |||
# Now add /dev/bcache1 to out volume group:\ | |||
## create a Physical Volume: <code>pvcreate /dev/bcache1</code> | |||
## add it to our Volume Group: <code>vgextend BCACHE /dev/bcache1</code> | |||
Now /dev/sda2 is an <b>cached</b> integral part of the volume group. You can allocate all space to /home, but to allow some further testing <b>don't do that yet</b>! | |||
}} | }} |
Revision as of 13:30, 12 October 2013
Description
This page describes a test case for bcache-tools; "/home on bcache using LVM".
This page describes a test case for bcache-tools, Bcache is a Linux kernel block layer cache. It allows one or more fast disk drives such as flash-based solid state drives (SSDs) to act as a cache for one or more slower hard disk drives. The bcache-tools package contains the utilities for manipulating bcache
Testing covers not only bcache-tools but also the interaction between bcache-tools and other packages: kernel, util-linux, dracut and lvm2.
Once your fresh Fedora 20 system is running, we will "move" /home to a Logical Volume (LVM) on a bcache device. Because of the flexibility that LVM provides the approach is quite different from page 1.A, for example we'll start by using sda4!
Prerequisites
The prerequisites for running the bcache-tools testcases can be found on this page
In this test case we'll need /dev/sda4 to build a new Volume Group on bcache.
Setup
Do the following steps:
- Open terminal
- Switch to root user:
su -
First of all we have to make sure no traces of bcache superblocks are left on /dev/sda4 and /dev/sdb1. So before installing bcache-tools do the following:
- update util-linux to the latest version (2.24 is required):
yum update util-linux
- Wipe whatever is on the two partitions:
wipefs -a /dev/sda4
wipefs -a /dev/sdb1
- Next install bcache tools and lvm2:
yum install bcache-tools lvm2
- reboot so bcache-tools is processed well
How to test
Now create an use the bcache devices:
- Make /dev/sda4 a bcache backing device:
make-bcache -B /dev/sda4
- Make /dev/sdb1 a bcache caching device:
make-bcache -C /dev/sdb1
- Note the set uuid and attach /dev/sdb1 to /dev/bcache0:
echo <set uuid> > /sys/block/bcache0/bcache/attach
Now you have a bcache device: /dev/bcache0
- use "bcache-status -s" to see details about your bcache device.
- create a Physical Volume:
pvcreate /dev/bcache0
- create a Volume Group:
vgcreate BCACHE /dev/bcache0
- create a Logical Volume:
lvcreate -L 2G -n HOME BCACHE
- create a filesystem:
mkfs -t ext4 -L HOME /dev/BCACHE/HOME
This will be our new /home device. To use it first move the current /home to another mount point:
- replace /home entry in your /etc/fstab:
LABEL=HOME /home ext4 defaults 1 2
- If needed copy your current /home to the new /home:
mkdir /home.old
umount /home
mount /dev/sda2 /home.old
mount /home
cp -ax /home.old/* /home
umount /home.old
rmdir /home.old
Now you have a system with /home on LVM2 on bcache. Next we can reuse the old /home disk space:
- First wipe all metadata:
wipefs -a /dev/sda2
- Make /dev/sda2 a bcache backing device:
make-bcache -B /dev/sda2
- Note the fact that a new /dev/bcache1 device is created
- Retrieve the cset.uuid from your /dev/sdb1 caching device:
bcache-super-show /dev/sdb1
- Attach /dev/sdb1 also to /dev/bcache1:
echo <cset.uuid> > /sys/block/bcache1/bcache/attach
There are two bcache devices now: /dev/bcache0 and /dev/bcache1 both using /dev/sdb1 as a caching device. The numbering of the bcache devices happens dynamically during boot, but until you reboot you can safely assume /dev/bcache0 uses /dev/sda4 as a backing device and /dev/bcache1 uses /dev/sda2 as a back device.
- use "bcache-status -s" to see details about your bcache devices.
- Now add /dev/bcache1 to out volume group:\
- create a Physical Volume:
pvcreate /dev/bcache1
- add it to our Volume Group:
vgextend BCACHE /dev/bcache1
- create a Physical Volume:
Now /dev/sda2 is an cached integral part of the volume group. You can allocate all space to /home, but to allow some further testing don't do that yet!
- reboot your system to see if it boots OK.
- do some other tests generating I/O on /home if you like
Expected Results
- All steps complete without errors
Optional
The original /home partition is no longer used, so we can reclaim its disk space by adding it to the volume group:
- First wipe all metadata:
wipefs -a /dev/sda2
- Make /dev/sda2 a bcache backing device:
make-bcache -B /dev/sda2
- Note the fact that a new /dev/bcache1 device is created
- Retrieve the cset.uuid from your /dev/sdb1 caching device:
bcache-super-show /dev/sdb1
- Attach /dev/sdb1 also to /dev/bcache1:
echo <cset.uuid> > /sys/block/bcache1/bcache/attach
There are two bcache devices now: /dev/bcache0 and /dev/bcache1 both using /dev/sdb1 as a caching device. The numbering of the bcache devices happens dynamically during boot, but until you reboot you can safely assume /dev/bcache0 uses /dev/sda4 as a backing device and /dev/bcache1 uses /dev/sda2 as a back device.
- use "bcache-status -s" to see details about your bcache devices.
- Now add /dev/bcache1 to out volume group:\
- create a Physical Volume:
pvcreate /dev/bcache1
- add it to our Volume Group:
vgextend BCACHE /dev/bcache1
- create a Physical Volume:
Now /dev/sda2 is an cached integral part of the volume group. You can allocate all space to /home, but to allow some further testing don't do that yet!