Rolffokkens (talk | contribs) (Created page with "The various bcache test cases require some preparation. === Limitations === There's no "easy way" to convert an existing filesystem to a bcache based filesystem: bcache is an...") |
Rolffokkens (talk | contribs) No edit summary |
||
| Line 26: | Line 26: | ||
* A desire to break software | * A desire to break software | ||
[[Category: | [[Category:Package_bcache-tools_test_cases]] | ||
Revision as of 18:23, 10 October 2013
The various bcache test cases require some preparation.
Limitations
There's no "easy way" 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 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 how to use the Linux command line (There's no graphical installer yet)
- A desire to break software