From: Dan Merillat <dan.merillat@gmail.com>
To: BTRFS <linux-btrfs@vger.kernel.org>
Subject: [PATCH v2 0/1] btrfs-progs: optionally restore metadata
Date: Tue, 21 Apr 2015 01:48:40 -0400 [thread overview]
Message-ID: <5535E4B8.9000909@gmail.com> (raw)
Changes since v1:
* Documented in the manpage
* Added to usage() for btrfs restore
* Made it an optional flag (-m/--restore-metadata)
* Use endian-safe macros to access the on-disk data.
* Restore the proper mtime instead of atime twice.
* Restore owner and mode
* Restore metadata for directories as well as plain files.
* Since it's now explicitly requested, errors are fatal
unless ignore_errors is requested.
I tested this on the array I'm restoring, it looks sane to me.
Thanks to Noah Massey for the patch review, and Duncan for the
prompt to add owner/permissions to the patch.
Symlinks and hardlinks are beyond the scope of these changes, I'll look
into them if this looks good to everyone.
next reply other threads:[~2015-04-21 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 5:48 Dan Merillat [this message]
2015-04-22 17:01 ` [PATCH v2 0/1] btrfs-progs: optionally restore metadata David Sterba
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=5535E4B8.9000909@gmail.com \
--to=dan.merillat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox