From: Chris Mason <chris.mason@oracle.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 08:57:40 -0400 [thread overview]
Message-ID: <1222261060.7160.168.camel@think.oraclecorp.com> (raw)
In-Reply-To: <200809232034.21750.phillips@phunq.net>
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.
In btrfs there's no need to merge. The original is still there and you
just use it instead of the snapshot. Both the original and the snapshot
are writable, you can pick whichever one you want to continue forward
with.
Said a different way, the underlying metadata structures and
capabilities of the snapshot and the original are the same. The only
difference between the two is their starting state.
-chris
prev parent reply other threads:[~2008-09-24 12:57 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
2008-09-24 10:27 ` Tomasz Torcz
2008-09-24 12:57 ` Chris Mason [this message]
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=1222261060.7160.168.camel@think.oraclecorp.com \
--to=chris.mason@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox