From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID 6 corrupted
Date: Thu, 18 May 2017 06:08:56 +0000 (UTC) [thread overview]
Message-ID: <pan$5e76f$e72f3dc7$e211b36e$44e19024@cox.net> (raw)
In-Reply-To: 20170518032956.axcluisxusxelmx6@angband.pl
Adam Borowski posted on Thu, 18 May 2017 05:29:57 +0200 as excerpted:
> On Thu, May 18, 2017 at 04:09:38AM +0200, Łukasz Wróblewski wrote:
>> Thanks guys.
>>
>> I will try when stable 4.12 comes out.
>
> It won't come out for ~2.5 months. I'd recommend building the -rc,
> recovering, then going back to a stable kernel.
?? 4.12-rc1 is already out. rc-s normally come out weekly and there's
almost always 7-8 of them, depending on how Linus feels about the
stability of things in the last few rc-s and what his coming schedule
looks like.
So we should only be looking at another ~7 weeks until 4.12.0 release,
now. Where'd ~2.5 months come from? Were you including the two weeks of
commit window pre-rc1 that's already passed? That'd make it about 9-10
weeks, so about 2.5 months, but about half a month of that's already gone.
Or does Linus have a couple weeks of no-release holiday coming up? IIRC
he usually does releases even on holiday, tho, but he may delay opening
the commit window or delay an rc a couple days.
--
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
next prev parent reply other threads:[~2017-05-18 6:09 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 [this message]
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
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$5e76f$e72f3dc7$e211b36e$44e19024@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).