From: GEO <1g2e3o4@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup over writable snapshot
Date: Fri, 21 Feb 2014 15:44:17 +0100 [thread overview]
Message-ID: <2333267.X1am0Dsk8s@linuxpc> (raw)
In-Reply-To: <2285169.jbztTl7OC0@linuxpc>
First of all, I am sorry that I screw up the whole structure of the discussion
(I have not subscribed to the mailing list, and as Kai replied to the mailing
list only, I could not reply to his answer.)
Kai: Yeah, your point was neutral and I did never understand it otherwise.
Thank you for your answer!
I already had idea of creating a subvolume called DATA in my home directory,
however I find that pretty annoying, as most applications will open home by
default.
In fact I would find it more elegant to generally backup without making changes
to my file system structure in home.
I know that there other possibilities to do what I want, but I am asking
whether the initially described method would work reliably, given that the
user makes not a fundamental mistake himself.
I know it may sound stubborn but I am really interested if my method works
just as reliable as the other suggested methods.
As I am not having the level required to check the code myself, I am asking
here, in the hope someone knowing the code could state if it should work or
not.
Thank you all for your help!
next prev parent reply other threads:[~2014-02-21 14:44 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
2014-02-20 21:16 ` Kai Krakow
2014-02-21 14:44 ` GEO [this message]
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=2333267.X1am0Dsk8s@linuxpc \
--to=1g2e3o4@gmail.com \
--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 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.