From: Dan Merillat <dan.merillat@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] btrfs-progs: restore symlinks
Date: Sat, 25 Apr 2015 14:16:52 -0400 [thread overview]
Message-ID: <CAPL5yKcZyku16OGjW9c+P3F-+yKP2vriFsoexjKR_mBiWzTp-A@mail.gmail.com> (raw)
In-Reply-To: <pan$e7045$f8d3aef7$794e780e$da3a4c69@cox.net>
At this point I I'm done - after writing the symlink patch I restored
everything of importance off my array to a scratch disk, wiped the
array and am in the process of copying everything back. I'll keep an
eye on this thread if changes need to be made to my patches, but
hopefully I won't be needing btrfs restore for a few more years!
On Fri, Apr 24, 2015 at 12:38 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> Dan Merillat posted on Thu, 23 Apr 2015 12:47:29 -0400 as excerpted:
>
>> Hopefully this is sufficiently paranoid, tested with PATH_MAX length
>> symlinks, existing files, insufficient permissions, dangling symlinks. I
>> think I got the coding style correct this time, I'll fix and resend if
>> not.
>>
>> Includes a trivial fix from my metadata patch, the documentation got
>> lost in the merge.
>
> Thanks for all this. I've only had to use restore once and hopefully
> won't be using it again in the near future, but having it restore the
> metadata and symlinks as well would surely have made the experience
> easier. There's a lot of people going to benefit from these patches over
> time as btrfs gains usage and the inevitable breakage happens to some of
> those filesystems. =:^/
>
> --
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-04-25 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 16:47 [PATCH 0/3] btrfs-progs: restore symlinks Dan Merillat
2015-04-23 16:50 ` [PATCH 1/3] btrfs-progs: restore: document metadata restore Dan Merillat
2015-04-23 16:51 ` [PATCH 2/3] btrfs-progs: separate the overwrite check Dan Merillat
2015-04-24 15:24 ` David Sterba
2015-04-25 18:19 ` Dan Merillat
2015-04-29 15:38 ` David Sterba
2015-04-23 16:52 ` [PATCH 3/3] btrfs-progs: optionally restore symlinks Dan Merillat
2015-04-24 4:38 ` [PATCH 0/3] btrfs-progs: " Duncan
2015-04-25 18:16 ` Dan Merillat [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=CAPL5yKcZyku16OGjW9c+P3F-+yKP2vriFsoexjKR_mBiWzTp-A@mail.gmail.com \
--to=dan.merillat@gmail.com \
--cc=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).