From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup over writable snapshot
Date: Thu, 20 Feb 2014 11:03:22 +0000 (UTC) [thread overview]
Message-ID: <pan$70982$400c23a8$2994c48a$4db2a63a@cox.net> (raw)
In-Reply-To: 99gfta-695.ln1@hurikhan77.spdns.de
Kai Krakow posted on Wed, 19 Feb 2014 21:20:23 +0100 as excerpted:
> Duncan had a nice example in this list how to migrate
> directories to subvolumes by using shallow copies: "mv dir dir.old &&
> btrfs sub create dir && cp -a -- reflink=always dir.old/. dir/. && rm
> -Rf dir.old".
FWIW, that was someone else. I remember seeing it and I may well have
been involved in some aspect of the discussion and thus might have quoted
it, but my particular use-case doesn't involve a lot of subvolumes or
snapshots, so I don't typically get quite that deep into the command-
detail in subvolume discussions as I've simply not had the necessary
personal experience in that area to properly discuss at that level. (Tho
it's certainly typical of what I might post in other areas, just not that
one.)
--
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-02-20 11:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 13:45 Incremental backup over writable snapshot GEO
2014-02-19 17:00 ` Chris Murphy
2014-02-19 18:57 ` GEO
2014-02-20 13:20 ` GEO
2014-02-20 23:04 ` Kai Krakow
[not found] ` <2285169.jbztTl7OC0@linuxpc>
2014-02-19 17:26 ` Chris Murphy
[not found] ` <16991840.tqyQc6bZHr@linuxpc>
2014-02-19 17:51 ` Chris Murphy
2014-02-19 20:20 ` Kai Krakow
2014-02-20 3:31 ` Kai Krakow
2014-02-20 11:03 ` Duncan [this message]
2014-02-20 21:16 ` Kai Krakow
2014-02-21 14:44 ` GEO
2014-02-21 18:56 ` Kai Krakow
2014-02-27 13:10 ` GEO
2014-02-28 6:54 ` Duncan
2014-02-27 14:36 ` GEO
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$70982$400c23a8$2994c48a$4db2a63a@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).