From: Steven Haigh <netwiz-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Adding caching to existing volumes?
Date: Sun, 20 Jan 2013 19:02:46 +1100 [thread overview]
Message-ID: <50FBA4A6.7020709@crc.id.au> (raw)
In-Reply-To: <17989056.10.1358618905144.JavaMail.root@zimbra>
On 20/01/2013 5:08 AM, Roy Sigurd Karlsbakk wrote:
> Hi all
>
> As far as I can understand from the bcache docs, a volume cached with bcache, must be formatted and setup for bcache in the first place. I come from a ZFS environment, where adding SLOG or L2ARC is done dynamically, so I have a few questions:
>
> - Would it be somewhat possible to add caching to an existing volume and its data?
> - What would happen if the cache device dies - does the whole filesystem become inaccessible?
I've actually been wondering a bit about this - its not exactly clear in
the docs as to what I should do to set up bcache.
In my case, I have a RAID6 over 4 x 2Tb drives. It lives as /dev/md2.
/dev/md[01] are RAID1 on a pair of 80Gb drives for boot and LVM.
As the system is a Xen Dom0, all the DomU (guests) run from their own LV
on the RAID6. So - it would make sense to add bcache to /dev/md2.
I'm a bit confused from reading the docs if I can attach to the existing
/dev/md2 or I have to create something from scratch. Obviously,
attaching to an existing RAID device is going to be the preferred method.
Covering this in the docs or even on the web site would probably be
beneficial for a lot of people - especially as I feel that this is
getting closer to be merged with the upstream kernel.
--
Steven Haigh
Email: netwiz-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
next prev parent reply other threads:[~2013-01-20 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 18:08 Adding caching to existing volumes? Roy Sigurd Karlsbakk
2013-01-20 8:02 ` Steven Haigh [this message]
[not found] ` <50FBA4A6.7020709-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org>
2013-01-22 23:15 ` Kent Overstreet
[not found] ` <20130122231547.GF26407-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-01-22 23:26 ` Steven Haigh
[not found] ` <50FF2016.4020802-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org>
2013-01-22 23:42 ` James Harper
2013-01-23 17:17 ` Roy Sigurd Karlsbakk
2013-01-24 21:21 ` Kent Overstreet
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=50FBA4A6.7020709@crc.id.au \
--to=netwiz-ty1ak9q0ptwhxe+lvdladg@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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