From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Zheng Yan <zheng.yan@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: snapshot merging?
Date: Sun, 21 Sep 2008 16:31:41 +0200 [thread overview]
Message-ID: <48D65ACD.7030907@wpkg.org> (raw)
In-Reply-To: <48D657DB.7050601@oracle.com>
Zheng Yan schrieb:
> Tomasz Chmielewski wrote:
>> At the beginning of August, Mikulas Patocka posted to linux-kernel
>> mailing list about adding snapshot merging to LVM[1].
>>
>> Basicaly, snapshot merging means that it is possible to turn a snapshot
>> back into its origin.
>>
>> Using LVM, however, means that you need to have free place outside of
>> the filesystem (i.e., in physical volume) to make snapshots, which is
>> not always possible on workstations and some servers.
>>
>> Is something similar available, or planned, for btrfs? I didn't find
>> anything similar on "btrfs design" page in the wiki.
>>
> Writeable snapshot has been available in btrfs for a long time.
Writeable snapshots and snapshot merging are two different things.
>> [1] http://kerneltrap.org/Linux/LVM_Snapshot_Merging
>>
> Writeable snapshot means you can mount/modify snapshots as you like.
> In other words, btrfs does snapshot merging automatically.
With LVM, you can also modify snapshots as you like, but it doesn't mean
LVM supports snapshot merging right now (that is, you have to apply the
patches described on the page above to have "snapshot merging" feature).
Maybe let me show you an example:
0) you have your "original" root filesystem
1) you make a snapshot of your rootfs
2) you upgrade your distribution (version 1.0 -> version 2.0-alpha)
3) you realise that some of the things don't work as expected - you mark
that your snapshot should be turned into an original
4) you reboot (as your rootfs is mounted, you have to) and from now on
your snapshot turns into the original from point 0.
Of course, one could boot off a live CD and copy the snapshot into the
original, but that involves additional operating system to be booted.
Or, you could copy data from snapshot to the original while your system
is running, but that could be risky for running programs (you replace
libc, lots of libraries, binaries etc.).
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-09-21 14:31 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 [this message]
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
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=48D65ACD.7030907@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-btrfs@vger.kernel.org \
--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.