[Date Prev][Date Next] [Thread Prev][Thread Next]
Re: [lvm-devel] cache support
- From: "Paul B. Henson" <henson acm org>
- To: "'LVM2 development'" <lvm-devel redhat com>
- Subject: Re: [lvm-devel] cache support
- Date: Tue, 11 Mar 2014 16:54:37 -0700
> From: Brassow Jonathan
> Sent: Wednesday, February 12, 2014 9:40 AM
> I'll let others weigh-in on the overhead of introducing thin-provisioning.
> However, my experience is that the overhead is very small and the benefit
> very large.
So I think I'd like to try out your recommendation of using thin
provisioning to allow dm-cache to cache all of my lv's, and was wondering if
you guys had any rough idea on when you might release a version of lvm2
with support for cache devices? The box in question is pseudo-production,
and while I think I'm willing to risk a freshly released new feature, I
don't think I want to go quite so far as to run git head on it ;).
The intention is to allow insertion of a cache device live with no
disruption in service, right? So theoretically I could get the thin
provisioned pool all set up now and start using it, and then when the
version with cache support is released, transparently slip in the cache
Is there a recommended kernel version for thin provisioning? Right now I'm
running 3.12, but I thought I saw a bug recently fly by involving thinpool
metadata corruption that's going to be fixed in 3.14, would it be better to
wait for a stable release of 3.14?
>From reading mailing list archives, if your metadata volume runs out of
space, your entire thin pool is corrupted? And historically you were unable
to resize or extend your metadata volume? I see a number of mentions of that
ability coming soon, but didn't see anything actually announcing it was
available. At this point, is the size of the metadata volume still fixed as
of initial creation?
The intended size of my thinpool is going to be about 3.64TB:
/dev/md3 vg_vz lvm2 a-- 3.64t 3.61t
Based on the recommendation below of 1/1000 of that for metadata, that would
be about 3.75GB. This pool is going to have *lots* of snapshots, there are
going to be a set of filesystems for a template vm, each of which will be
snapshot'd/cloned when a new vm is created, and then all of those will have
snapshots for backups. Given that, would 3.75GB for the metadata volume be
sufficient, or would it be better to crank it up a little?
Given /dev/md3 is my "slow" device (raid10 of 4 x 2TB), and /dev/md2 is my
"fast" device (raid1 of 2 x 256G SSD), plugging into your example gives me:
# vgcreate vg_vz /dev/md3 /dev/md2
# lvcreate -l 953800 -n thinpool vg_vz /dev/md3
# lvcreate -L 3.75G -n thinpool_metadata /dev/md2
# lvconvert --thinpool vg_vz/thinpool --poolmetadata thinpool_metadata
At this point, I would have a thinpool ready to use, and can work with it
until a version of lvm2 is released with cache support, at which point I
# lvcreate --type cache_pool -l 100%PVS -n cachepool vg /dev/md2
# lvconvert --type cache --cachepool vg/cachepool vg/thinpool
To transparently add the cache device to my existing thinpool?
> I imagine the steps being something like this:
> # Create your VG with slow and fast block devices
> 1~> vgcreate vg /dev/slow_sd[abcdef]1 /dev/fast_sd[abcde]1
> # Create data portion of your thin pool using all your slow devices
> 2~> lvcreate -l <all slow dev extents> -n thinpool vg
> # Create the metadata portion of your thin pool
> # use fast devs to keep overhead down
> # use raid1 to provide redunancy
> 3~> lvcreate --type raid1 -l <1/1000th size of data LV> -n
> vg /dev/fast_sd[ab]1
> # Create cache pool LV that will be used to cache the data portion of the
> # You can use 'writethrough' mode to speed up reads, but still have
> hit the slow dev
> # or you can create the data&metadata areas of the cachepool separate
> using raid and then
> # convert those into a cache pool... lots of options here to improve
> redundancy. I'm working
> # on man page changes/additions to make this clear and simple. For now,
> we'll just create
> # a cachepool simple LV.
> 4~> lvcreate --type cache_pool -L <desired cache size> -n cachepool vg
> # Use the cache pool to create a cached LV of the thin pool data device
> 5~> lvconvert --type cache --cachepool vg/cachepool vg/thinpool
> # The data portion of your 'thinpool' LV is now cached.
> # Make the thinpool using the cached data LV 'thinpool' and the fast
> metadata LV 'thinpool_metadata'
> 6~> lvconvert --thinpool vg/thinpool --poolmetadata thinpool_metadata
> You now have a very fast thin pool from which you will create thin volumes
> and snapshots. Everything is cached with low overhead.
> 7~> lvcreate -T vg/thinpool -n my_lv1 -V 200G
> 8~> lvcreate -T vg/thinpool -n my_lv2 -V 200G
> N.B. Note that you must specify '--with-cache=internal' when configuring
> LVM - cache is off by default until it is no longer considered
> You should be using dm-cache kernel module version 1.3.0+. Support for
> 'lvconvert --type cache[-pool]' was only just added this morning.
[Date Prev][Date Next] [Thread Prev][Thread Next]