| Summary: | Build LVM2 with the --with-cache=internal option | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Theodoros Kalamatianos <thkala> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | thierry.vignaud |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | lvm2 | CVE: | |
| Status comment: | |||
|
Description
Theodoros Kalamatianos
2014-11-09 02:44:40 CET
Manuel Hiebel
2014-11-10 23:23:03 CET
Keywords:
(none) =>
Triaged I converted my Cauldron root filesystem to lvmcache. Performance-wise it seems to be worth it, even in the default write-through mode. That said, I had to jump through a few hoops: - I updated the LVM2 package to version 2.02.114, which enables lvmcache by default and fixes quite a few things. - I compiled and installed the thin-provisioning-tools package (https://github.com/jthornber/thin-provisioning-tools) - see below. - I modified the dracut configuration to include the thin-provisioning-tools binaries in the initramfs, using the `install_items+=...' option. Without this modification the system would not boot, because lvm2 requires these binaries when a thin or cached LV exists. - I regenerated the initramfs and ran `lilo' to update the bootloader - GRUB users would not need this step. All in all, it still seems quite easy to shoot yourself in the foot with lvmcache. The LVM2 people are making good progress w.r.t. making things safer, but it's probably not for the faint-hearted just yet. Thomas, this is done by other distros, eg: Fedora. I think it's safe to add --with-cache=internal Though it's now the default, so we can close this bug as OLD Resolution:
(none) =>
OLD |