From: Martin Steigerwald <martin@lichtvoll.de>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: incremental full file backups to smaller mediums possible?
Date: Sat, 18 Apr 2015 10:14:58 +0200 [thread overview]
Message-ID: <1489496.v0bc8xWMtg@merkaba> (raw)
In-Reply-To: <1429311803.8371.58.camel@scientia.net>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Am Samstag, 18. April 2015, 01:03:23 schrieb Christoph Anton Mitterer:
> On Thu, 2015-04-09 at 16:33 +0000, Hugo Mills wrote:
> > btrfs sub find-new might be more helpful to you here. That will
> >
> > give you the list of changed files; then just feed that list to your
> > existing bin-packing algorithm for working out what goes on which
> > disks, and you're done.
>
> hmm that sounds interesting, but
> a) it lacks much documentation (how does that with the generations work?
> when is there a new generation? what, if the generation overflows?)
I have no idea about when there is a new generation. I think it depends on
the commit intervall.
You can see the current generation with:
merkaba:~> btrfs subvol show / | grep Generation
Generation (Gen): 468143
> b) it seems to only show me new files, but not files that have been moved,
> or removed, or when properties have changed.
It should show renamed or moved files. But yeah, if it does, at least not
in a way that shows that a rename or move operation took place.
> c) it seems to work only for one subvolume?
Its per subvolume, I think. Thats why it is under "btrfs subvolume"
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-04-18 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 16:14 incremental full file backups to smaller mediums possible? Christoph Anton Mitterer
2015-04-09 16:33 ` Hugo Mills
2015-04-17 23:03 ` Christoph Anton Mitterer
2015-04-18 8:14 ` Martin Steigerwald [this message]
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=1489496.v0bc8xWMtg@merkaba \
--to=martin@lichtvoll.de \
--cc=calestyo@scientia.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).