All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Woodward <markw@mohawksoft.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshots
Date: Thu, 16 Feb 2012 11:04:08 -0500	[thread overview]
Message-ID: <4F3D28F8.2060009@mohawksoft.com> (raw)
In-Reply-To: <20120216154301.GA13948@redhat.com>

On 02/16/2012 10:43 AM, Mike Snitzer wrote:
> On Thu, Feb 16 2012 at  9:42am -0500,
> Mark Woodward<markw@mohawksoft.com>  wrote:
>
>> On 02/16/2012 08:57 AM, Mike Snitzer wrote:
>>> On Thu, Feb 16 2012 at  8:25am -0500,
>>> Mark Woodward<markw@mohawksoft.com>   wrote:
>>>
>>>> I have been looking into LVM2 for a while now and while I think it
>>>> is useful for a range of applications, its seems pretty limited in
>>>> overall scope.
>>>>
>>>> Is there any active development happening? Most of the code seems
>>>> like bug-fixes or minor tweaks. Is the snapshot system being
>>>> improved? Specifically, snapshots of snapshots? thin provisioned
>>>> snapshots or auto-expand (i.e. snapshots don't run out of space).
>>>> If you look at technologies like ZFS snapshots are far better
>>>> supported, but ZFS will probably never be real under Linux, and it
>>>> really is far more than is really needed.
>>>>
>>>> So, I guess my questions are these: Is LVM in maintenance mode or is
>>>> there active development? If it is being actively developed, is
>>>> there a road map and is there a group or site specifically dedicated
>>>> to the development?
>>> Um, where are you even getting this idea that LVM2 is in maintenance
>>> mode?  Or that snapshots haven't improved?
>>>
>>> Sorry to come off defensive but your entire post is founded on incorrect
>>> understanding.
>> Understood, I apologize.
>>> Anyway, if you look at the change history of the lvm2 repository (be it
>>> cvs or git, cvs commits are mirrored to git) you'll see there have been
>>> regular changes flowing in and most recently a very extensive evolution
>>> of the code to add support for thin provisioning with highly efficient
>>> snapshots (ala btrfs or ZFS).
>> I guess I missed that. I need to check out the changes, looks like
>> you have auto-grow with monitoring? I was looking more towards the
>> "snapshots of snapshots" ability. Is that on the radar?
> recursive snapshots of arbitrary depth (snapshot of snapshots ...) are
> already supported with the new thinp snapshots.
>
> Please review the upstream Linux>= 3.2 kernel code/docs too, it has
> more documentation of the underlying capabilities, e.g.:
>
> Documentation/device-mapper/thin-provisioning.txt
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/device-mapper/thin-provisioning.txt
>
> (the "Introduction" being the most approachable overview)
OK, that's where I missed it. I looked at the snapshots description. It 
is now part of thin-provisioning. Got it. Will it be in the 2.6 kernel 
or will there need to be an upgrade to 3.x series?

  reply	other threads:[~2012-02-16 16:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 13:25 [linux-lvm] Snapshots Mark Woodward
2012-02-16 13:57 ` Mike Snitzer
2012-02-16 14:05   ` Marco Pizzoli
2012-02-17 15:20     ` Mike Snitzer
2012-02-16 14:42   ` Mark Woodward
2012-02-16 15:18     ` Stuart D. Gathman
2012-02-16 15:54       ` Mike Snitzer
2012-02-17  4:46         ` Stuart D. Gathman
2012-02-17 13:56           ` Mike Snitzer
2012-02-16 16:51       ` Bryn M. Reeves
2012-02-16 15:43     ` Mike Snitzer
2012-02-16 16:04       ` Mark Woodward [this message]
2012-02-16 16:09         ` Mike Snitzer
  -- strict thread matches above, loose matches on Subject: below --
2009-09-17 14:24 Jon Hardcastle
2009-09-17 14:37 ` Peter Keller
2009-09-10 23:25 jonr
2009-09-11  9:14 ` Peter Keller
2009-09-11 13:39 ` André Gillibert
2001-10-18 20:35 [linux-lvm] snapshots Robert Dyas
2001-10-18 21:11 ` Andreas Dilger

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=4F3D28F8.2060009@mohawksoft.com \
    --to=markw@mohawksoft.com \
    --cc=linux-lvm@redhat.com \
    --cc=snitzer@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.