From: Matt M <fakeg...@gmail.com>
To: voidlinux@googlegroups.com
Subject: SSD caching via LVM slightly broken
Date: Mon, 2 Mar 2015 13:47:43 -0800 (PST) [thread overview]
Message-ID: <b2c50220-0e7c-4242-a54c-5a4930566449@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 703 bytes --]
The only thing holding me back from fully migrating to Void was SSD caching
using dm-cache. when setting up my lvm configuration and rebooting, the
system would get upset and drop to shell complaining that it didn't know
the version of _cache_ kernel module.
The problem was twofold:
1) had to force dm-cache kernel module to load in dracut.conf, dm-cache
wouldn't load into initramfs without being forced.
2) file /etc/runit/core-services/03-filesystems.sh failed at "vgchange
--sysinit -a y" as it needs the command cache_check, a symlink to
pdata-tools
TL;DR - Solved the problem by forcing dracut to play along, and then
installing thin-provisioning-tools from git.
[-- Attachment #1.2: Type: text/html, Size: 832 bytes --]
next reply other threads:[~2015-03-02 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 21:47 Matt M [this message]
2015-03-08 10:32 ` Juan RP
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2c50220-0e7c-4242-a54c-5a4930566449@googlegroups.com \
--to="fakeg..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).