From: "Amir G." <amir73il@users.sourceforge.net>
To: Alex Bligh <alex@alex.org.uk>
Cc: Joe Thornber <thornber@redhat.com>,
Lukas Czerner <lczerner@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
linux-ext4@vger.kernel.org, tytso@mit.edu,
linux-kernel@vger.kernel.org, lvm-devel@redhat.com,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots)
Date: Sat, 11 Jun 2011 12:44:16 +0300 [thread overview]
Message-ID: <BANLkTik8Oac+5Ci7Y9VvNUqv-DaYmPkWZA@mail.gmail.com> (raw)
In-Reply-To: <843433D5F73C864182AC91B8@nimrod.local>
On Sat, Jun 11, 2011 at 11:18 AM, Alex Bligh <alex@alex.org.uk> wrote:
>
>
> --On 11 June 2011 08:49:08 +0100 Joe Thornber <thornber@redhat.com> wrote:
>
>> I am also convinced multisnap wont be suitable for every use case.
>
> I'm surprised by one thing ext 4 snapshots doesn't seem to do: I would have
> thought the "killer feature" for doing snapshots in the fs rather than in
> the block layer would be the ability to snapshot - and more importantly
> roll back - only parts of the directory hierarchy.
>
> (I've only read the URLs Amir sent, so apologies if I've missed this)
>
No need for apologies.
There is no per-directory snapshot nor rollback with ext4 snpshots.
It is possible to configure a part of the directory hierarchy to be excluded
from future snapshots, but not to delete it selectively from past snapshots.
Amir.
next prev parent reply other threads:[~2011-06-11 9:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimyBGfg4+ovGsiGqpCz345qVmU_7A@mail.gmail.com>
[not found] ` <BANLkTik20iYN4c9faKD9dzerehazWTwTFw@mail.gmail.com>
2011-06-10 8:08 ` LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots) Amir G.
2011-06-10 9:01 ` Lukas Czerner
2011-06-10 10:11 ` Joe Thornber
2011-06-10 14:15 ` Amir G.
2011-06-10 15:01 ` Joe Thornber
2011-06-11 4:01 ` Amir G.
2011-06-11 7:49 ` Joe Thornber
2011-06-11 8:18 ` Alex Bligh
2011-06-11 9:44 ` Amir G. [this message]
2011-06-11 5:41 ` Amir G.
2011-06-11 7:35 ` Joe Thornber
2011-06-11 9:58 ` Amir G.
2011-06-13 8:50 ` Joe Thornber
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=BANLkTik8Oac+5Ci7Y9VvNUqv-DaYmPkWZA@mail.gmail.com \
--to=amir73il@users.sourceforge.net \
--cc=alex@alex.org.uk \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@redhat.com \
--cc=snitzer@redhat.com \
--cc=thornber@redhat.com \
--cc=tytso@mit.edu \
/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).