From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID 6 corrupted
Date: Sat, 20 May 2017 02:30:48 +0000 (UTC) [thread overview]
Message-ID: <pan$f0a91$d5a6b148$d2f11d14$5118d69e@cox.net> (raw)
In-Reply-To: 20170519085527.GD24459@reaktio.net
Pasi Kärkkäinen posted on Fri, 19 May 2017 11:55:27 +0300 as excerpted:
> On Thu, May 18, 2017 at 06:12:22AM +0000, Duncan wrote:
>> Roman Mamedov posted on Thu, 18 May 2017 10:17:19 +0500 as excerpted:
>>
>> > On Thu, 18 May 2017 04:09:38 +0200 ??ukasz Wróblewski <lw@nri.pl>
>> > wrote:
>> >
>> >> I will try when stable 4.12 comes out.
>> >> Unfortunately I do not have a backup.
>> >> Fortunately, these data are not so critical.
>> >> Some private photos and videos of youth.
>> >> However, I would be very happy if I could get it back.
>> >
>> > Try saving your data with "btrfs restore" first
>>
>> First post, he tried that. No luck. Tho that was with 4.4 userspace.
>> It might be worth trying with the 4.11-rc or soon to be released 4.11
>> userspace, tho...
>>
>>
> Try with 4.12-rc, I assume :)
No. btrfs restore is 100% userspace, so we're talking btrfs-progs (thus
the "userspace" specifier) version here, not kernel version.
And at the time 4.11-rc was the latest progs version, with 4.11 due
within a day or two, so "4.11-rc or soon to be released 4.11 userspace"
was correct.
Of course since then 4.11 userspace /has/ been released, so it'd be 4.11
without the -rc, now.
(When I got the CCed email I couldn't make heads or tails since I was
missing the thread context, tho the fact that I was dead tired probably
didn't help. I just checked the list, which I interface with as a
newsgroup on gmane.org's list2news service, after getting home from work
today, however, and there the entire thread is visible, as one would
expect for a newsgroup, so I could make sense of the context, and realize
it was a case of kernel version vs. userspace version confusion. Easy
enough to clarify... =:^)
--
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
prev parent reply other threads:[~2017-05-20 2:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 8:27 RAID 6 corrupted Łukasz Wróblewski
2017-05-17 9:45 ` Adam Borowski
2017-05-17 9:52 ` Duncan
2017-05-17 10:05 ` Duncan
2017-05-17 10:15 ` Adam Borowski
2017-05-18 2:09 ` Łukasz Wróblewski
2017-05-18 3:29 ` Adam Borowski
2017-05-18 6:08 ` Duncan
2017-05-18 8:34 ` Adam Borowski
2017-05-18 5:17 ` Roman Mamedov
2017-05-18 6:12 ` Duncan
2017-05-19 8:55 ` Pasi Kärkkäinen
2017-05-19 9:09 ` Roman Mamedov
2017-05-20 2:30 ` Duncan [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='pan$f0a91$d5a6b148$d2f11d14$5118d69e@cox.net' \
--to=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).