| Fedora Test Days | |
|---|---|
| |
| SSD Cache | |
| Date | 2013-10-13 |
| Time | all day |
| Website | QA/Fedora_20_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
The Test Day page is yet in construction. It will be ready for the Test Day - when this message is removed :) .
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on bcache based SSD Caching in Fedora 20. Although dm-cache is another SSD caching implementation, today we'll only focus on the bcache implementation.
General test objective
The objective of this Test day is to demonstrate a working Fedora 20 system using bcache. Te be more specific:
- The system boots OK; after booting bcache is operating as expected
- The system updates ("yum update") OK. After updating specifically the kernel the system boots OK.
- The system is bootable when the caching device is disabled.
Scope
The bcache implementation of SSD caching is a new feature (since kernel 3.9) and should be considered experimental. The focus of this Test day is to evaluate the alignment of bcache-tools with other relevant Fedora packages to support a good basis for experimenting with SSD caching:
- bcache-tools (version 0-0.14.20130909git or later)
- util-linux (version 2.24-0.1 or later)
- dracut (version 034 or later)
- lvm2 (version 2.02.102-1 or later)
- kernel (version 3.9 or later)
Anaconda support for bcache is expected to be available not until Fedora 21, so this is not in scope for the test day.
In general issues related to the bcache kernel driver are not in scope; SSD caching is not production yet so they should be addressed in the regular development process. This includes performance related issues. Only when the Test day demonstrates a unworkable situation, issues related to the bcache driver in the kernel are in scope on the Test day.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Kent Overstreet (py1hon)
- Quality Assurance - Igor Gnatenko (ignatenkobrain), Rolf Fokkens (rolffokkens)
Prerequisite for the Test Day
Limitations
There's no "easy way" yet to convert an existing filesystem to a bcache based filesystem: bcache is an additional block layer that writes its own superblock on the underlying block devices. There is a blocks [[1]] tool under development, but for now the only solution is to backup your data some where, recreate your filesystem on a bcache device, and then restore the data.
Another limitation is the fact that bcache is EXPERIMENTAL. Although it works really well in general, you should be careful to store important data on it.
Physical or Virtual
Although performance (of course) is a very important aspect of SSD caching, testing it is not required on the test day. Because of this testing can be done both on physical and virtual hardware, on a true SSD or a HDD. There is however a slight preference to do the testing on real hardware, with a real SSD.
Whenever the terms HDD or SDD are used below, they can be both physical and virtual. The same is true for the terms "system", "CPU", "RAM`and "bootable media".
Hardware & Software requirements
- A fresh system:
* 10GB+ HDD * 2GB+ SSD * 256MB+ RAM * x86 CPU (32bit or 64bit) * internet connection
- bootable media containg Rawhide/F20 (?) netinst (?) image.
Other requirements
- Knowledge on how to build physical or virtual machines
- Knowledge on how to use the Linux command line (There's no graphical installer yet)
- A desire to break software
Further reading
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
- An updated Fedora 20 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
How to test?
Because Anaconda does not support bcache yet, the test may be executed following certain steps: preparation and test case 1 to test case 3. The end result will be a F20 system running its root filesystem on bcache. These steps are merely suggestions, to allow testing in limited time. Of course testers are free to choose other ways of testing. As a suggestion, testers can focus on the following criteria:
- Do the tools to create / manage bcache operate as expected?
- Are your 'bcached' filesystems automatically operational after a reboot?
- Are your 'bcached' filesystems automatically operational after a kernel update?
Each demonstrates the proper allignment of dracut, util-linux, lvm2 (when used), bcache-tools and the kernel.
Preparation: install F20
The first step is to do a minimal install:
- this is the fastest install
- it also saves time when copying the root filesystem during later test cases
- it allows to install other packages later (yum groupinstall) as part of the test activities.
Both the partitioning and the installation of Fedora can be done by any of the iso's in https://dl.fedoraproject.org/pub/alt/stage/, e.g. Fedora-20-Alpha-x86_64-netinst.iso.
Test Cases
Test case 1.A: /home on bcache (no LVM)
Once your fresh Fedora 20 system is running, we will "move" /home to a bcache device without using LVM.
Step by step instructions are available on this page
Test case 1.B: / on bcache (no LVM)
Now we have a stable system with /home on bcache, we can go forward and have / on bcache without using LVM.
Step by step instructions are available on this page.
Test case 2.A: /home on bcache (LVM)
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! Do the following steps:
- yum install bcache-tools lvm2
- 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/sda2: 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
- mkdir /home.old
- umount /home
- mount /dev/sda2 /home.old
- mount /home
- cp -ax /home.old/* /home
- umount /home.old
- build a new initramfs with dracut???
Now you have a system with /home on LVM2 on bcache.
- reboot your system to see if it boots OK.
- do some other testing if you like.
Test case 2.B: / on bcache (no LVM)
step 1: / on bcache with fallback
Now we have a stable system with /home on LVM on bcache, we can go forward and have / on bcache. Consider thought that bcache is EXPERIMENTAL!
To get / on bcache:
- create a Logical Volume: lvcreate -L 2G -n ROOTFS BCACHE
- create a filesystem: mkfs -t ext4 -L ROOTFS /dev/BCACHE/ROOTFS
- mount it: mount /dev/BCACHE/ROOTFS /mnt
- copy your current root filesystem to /mnt: cp -ax / /mnt
- edit /mnt/fstab so your root fs is mounted like: LABEL=ROOTFS / ext4 defaults 1 1
Now we have a duplicate root filesystem on /dev/BCACHE/ROOTFS. To use it we need to build a new initramfs:
- rename your current initramfs: mv /boot/initramfs...img /boot/initramfs...img.sav
- create a new initramfs: dracut -N
Now reboot your system. Edit your default grub entry:
- replace the root=UUID=... parameter in the "linux" line by: root=LABEL=ROOTFS
- remove any rd.lvm=0 occurrence
- boot it.
If all goes well, your system now boots fine and it's running on bcache!
- Edit your /etc/grub2.cfg file..
- .. duplicate the first "menuentry ... { ...}" (about 15 lines).
- Now change the first one and replace the root=UUID=... parameter in the "linux" line by root=LABEL=ROOTFS
- reboot again
Now your system should boot fine.
Participants
| User | IRC nickname |
|---|---|
| Igor Gnatenko | ignatenkobrain |
| Rolf Fokkens | rolffokkens |
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component bcache-tools. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
| User | /home on bcache (no LVM) | / on bcache (no LVM) | /home on bcache (LVM) | / on bcache (LVM) | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |