linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>
Subject: btrfs-subv-backup v0.3b
Date: Tue, 31 Oct 2017 10:45:46 -0400	[thread overview]
Message-ID: <289afe3e-53ad-3803-fb6d-28f3238e67ff@gmail.com> (raw)

A new version of btrfs-subv-backup has just been uploaded to github.
Yes, I know I skipped v0.2b, I actually did upload a version v0.2b, I 
just forgot to post anything about it here...

Changes since the last time I posted here:

v0.2b:
     * Updated the LICENSE file so that GitHub properly recognizes it as 
a 3-clause BSD license.
     * Tidied up README.md and clarified some things.
     * We now skip existing subvolumes that are where they are supposed 
to be instead of trying to replace them and throwing an error at the 
end.  This means you can restore on a partially restored tree.
     * Permissions and timestamps for subvolumes are copied correctly now.
     * If running as root, subvolume ownership is also copied correctly now.
     * You can now use the flag `--verbose` or `-v` to get some progress 
info.
     * Permissions and ownership are properly preserved for files and 
directories under restored subvolumes.
     * Added an optional dependency on the 'reflink' module [1].  If 
present on the system, it will be used by default when restoring subvolumes.
     * Added an option `--method` to explicitly specify what method to 
use for restoring subvolumes.

v0.3b:
     * Failures to call blkid are now non-fatal (they technically were 
already, but were being treated as fatal errors).
     * The reflink method for restoring subvolumes now falls back 
gracefully to the copy method if a reflink fails.
     * btrfs-subv-backup will now bail early if it is told to create a 
subvolume where a mount point already exists, instead of failing at the 
end of restoring the subvolume.
     * Added better info on dependencies to the README, and properly 
spell checked it.

                 reply	other threads:[~2017-10-31 14:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=289afe3e-53ad-3803-fb6d-28f3238e67ff@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=bernd.lentes@helmholtz-muenchen.de \
    --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).