linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <blackmagic02881@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: evms-devel@lists.sourceforge.net, linux-lvm@redhat.com
Subject: [linux-lvm] Re: [dm-devel] [RFC] Out of order snapshot deletion
Date: Fri, 12 Jan 2007 13:37:56 -0500	[thread overview]
Message-ID: <1168627076.2805.125.camel@localhost.localdomain> (raw)
In-Reply-To: <45A766F3.A9E3.000B.0@novell.com>

On Thu, 2007-01-11 at 22:19 -0700, Vijai Babu Madhavan wrote:
> Hi,
> 
> I thought I would bring this topic in a separate thread so that 
> it can be discussed independently.
> 
> As users start taking a bunch of snapshots and keep them as 
> backups, we see the following use pattern when the snapshots 
> get recycled.
> 
> Different snapshots have different life cycle. When some one 
> decides to keep 'x' snapshots, at the recycle phase, the least 
> recent does not necessarily get deleted.
> 
> As users want to keep the daily snapshots for a much longer period
> than the bi-hourly snapshots. In the same way, weekly snapshots 
> live longer than daily snapshots.
> 
> I think this is pretty much similar to the way the current backup tapes
> are managed.

make sense.

> 
> I want to know if this is the kind of use case that users are having or 
> the developers are thinking.
> 
> The reason why I am posting this is that this out of snapshot deletion
> scenario, poses some interesting challenges in the design on the solution 
> of multiple snapshots that share blocks with each other, as it is a lot easier 
> to design a solution where the least recent gets deleted always.

this does not hold true. for snapshot used as backup purpose, you 100%
can not assume the oldest or newest will be delete first. there is no
such rule.

and possibly, you create one snapshot base on policy and later mount it
and check data consistency. if it turns out to be a bad one, you want to
delete it. then you have no order to follow at all.

ps, any comment on http://sourceware.org/cluster/csnap/? this also try
to solve the current multiple snapshot issues.

thanks

Ming

> 
> Vijai
> 
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
-- 
http://blackmagic02881.wordpress.com/

  reply	other threads:[~2007-01-12 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  5:19 [linux-lvm] [RFC] Out of order snapshot deletion Vijai Babu Madhavan
2007-01-12 18:37 ` Ming Zhang [this message]
2007-01-12 18:51 ` [linux-lvm] RE: [dm-devel] " Wilson, Christopher J

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=1168627076.2805.125.camel@localhost.localdomain \
    --to=blackmagic02881@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=evms-devel@lists.sourceforge.net \
    --cc=linux-lvm@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 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).