All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anopolsky <erpo41@gmail.com>
To: Daniel Phillips <phillips@phunq.net>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
	Zheng Yan <zheng.yan@oracle.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: snapshot merging?
Date: Wed, 24 Sep 2008 02:54:16 -0600	[thread overview]
Message-ID: <1222246456.26395.16.camel@telesto> (raw)
In-Reply-To: <200809232034.21750.phillips@phunq.net>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

On Tue, 2008-09-23 at 20:34 -0700, Daniel Phillips wrote:
> On Sunday 21 September 2008 07:31, Tomasz Chmielewski wrote:
> > > Writeable snapshot has been available in btrfs for a long time.
> > 
> > Writeable snapshots and snapshot merging are two different things.
> 
> I think what Mikulas really means by "snapshot merging" is what we call
> "revert to snapshot" in ddsnap (google Zumastor ddsnap).  The latter is
> more appropriate terminology IMHO.  For a snapshotted volume, this just
> requires copying any blocks that belong to the snapshot and not the
> origin back to the origin.  Similarly, one could revert any snapshot
> "back" (quotes because there is not necessarily any relationship in
> time) to any other.  For a filesystem it will not be nearly so simple,
> because at best only part of the job can be done at the physical block
> level.

It took me a while to get what was meant by snapshot merging. Consider
this a vote for the "revert" terminology. :) Although, it calls into
question some of my assumptions about what people use snapshots for.

What do people use snapshots for?

Cheers,
Eric


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-09-24  8:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21 12:22 snapshot merging? Tomasz Chmielewski
2008-09-21 14:19 ` Zheng Yan
2008-09-21 14:31   ` Tomasz Chmielewski
2008-09-21 15:00     ` Zheng Yan
2008-09-24  3:34     ` Daniel Phillips
2008-09-24  8:54       ` Eric Anopolsky [this message]
2008-09-24 10:27         ` Tomasz Torcz
2008-09-24 12:57       ` Chris Mason

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=1222246456.26395.16.camel@telesto \
    --to=erpo41@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=phillips@phunq.net \
    --cc=zheng.yan@oracle.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.