From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: How does Suse do live filesystem revert with btrfs?
Date: Tue, 6 May 2014 16:26:48 +0000 (UTC) [thread overview]
Message-ID: <pan$4eac3$a2d76a4$a81e0fed$b4b18c9e@cox.net> (raw)
In-Reply-To: 20140505050459.GF10159@merlins.org
Marc MERLIN posted on Sun, 04 May 2014 22:04:59 -0700 as excerpted:
> On Mon, May 05, 2014 at 01:36:39AM +0100, Hugo Mills wrote:
>> I'm guessing it involves reflink copies of files from the snapshot
>> back to the "original", and then restarting affected services. That's
>> about the only other thing that I can think of, but it's got load of
>> race conditions in it (albeit difficult to hit in most cases, I
>> suspect).
>
> Aaah, right, you can use a script to see the file differences between
> two snapshots, and then restore that with reflink if you can truly get a
> list of all changed files.
> However, that is indeed not atomic at all, even if faster than rsync.
Would send/receive help in such a script?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-05-06 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 0:52 How does Suse do live filesystem revert with btrfs? Marc MERLIN
2014-05-04 23:26 ` Marc MERLIN
2014-05-05 0:36 ` Hugo Mills
2014-05-05 5:04 ` Marc MERLIN
2014-05-06 16:26 ` Duncan [this message]
2014-05-07 8:56 ` Marc MERLIN
2014-05-07 11:35 ` Duncan
2014-05-07 11:39 ` Marc MERLIN
2014-05-07 18:33 ` Goffredo Baroncelli
2014-05-05 3:23 ` Chris Murphy
2014-05-05 6:50 ` Marc MERLIN
2014-05-05 2:39 ` Duncan
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='pan$4eac3$a2d76a4$a81e0fed$b4b18c9e@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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).