All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: dm-devel@redhat.com
Subject: Re: [RFC] zodcache - auto-start dm-cache devices
Date: Fri, 18 Dec 2015 18:01:59 -0600	[thread overview]
Message-ID: <n526pn$phb$1@ger.gmane.org> (raw)
In-Reply-To: <56747558.7030507@redhat.com>

On 12/18/2015 03:06 PM, Zdenek Kabelac wrote:
> Sure - as long as you do not need to solve any 'security/safety' points,
> you can do things in a simple way.

What security/safety concerns do you have with this approach?

> But how do you plan to support any power-failures and recoveries ?

A zodcache device is a dm-cache device built from several dm-linear
devices.  AFAICT, that's exactly what a LVM cache LV is, so I would
expect that they would handle such events in exactly the same way.

> When someone pick drive to other system - what is going to happen ?

If the system already has zodcache support then things should pretty
much "just work".  If not, it takes exactly one program to manually
start a device, and the only dependencies are dm-cache and libdevmapper.

> Are you going to write your own 'lvm2-like' tools to do the job ?

Absolutely not.  This is not intended to compete with LVM.  In fact, I
would expect that using zodcache devices as LVM PVs to be the most
use case.  (It's certainly what I'm doing.)

> Are you going to maintain this over long time period ?

If people use it, then yes.

> You really should have started from RFE on lvm2 enhancements to better
> suite
> your needs -  since IMHO there are no SIMPLE things when we talk about
> devices...

But isn't that the beauty of device mapper?  The hard work has already
been done, and I'm just adding the bits to set things up.  (I'm not
doing anything that couldn't be done with dmsetup.)

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================

  reply	other threads:[~2015-12-19  0:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18  6:16 [RFC] zodcache - auto-start dm-cache devices Ian Pilcher
2015-12-18  9:44 ` Joe Thornber
2015-12-18 16:07 ` John Stoffel
2015-12-18 16:55   ` Ian Pilcher
2015-12-18 17:39     ` Ian Pilcher
2015-12-18 18:53     ` John Stoffel
2015-12-18 18:51 ` Alasdair G Kergon
2015-12-18 19:44   ` John Stoffel
2015-12-18 20:01     ` Alasdair G Kergon
2015-12-18 20:50   ` Ian Pilcher
2015-12-18 21:06     ` Zdenek Kabelac
2015-12-19  0:01       ` Ian Pilcher [this message]
2015-12-19  0:53 ` Never mind (was [RFC] zodcache - auto-start dm-cache devices) Ian Pilcher
2015-12-19  1:53   ` John Stoffel
2016-01-04 15:52     ` Joe Thornber
2016-01-06 15:49       ` Ian Pilcher

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='n526pn$phb$1@ger.gmane.org' \
    --to=arequipeno@gmail.com \
    --cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.