From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Adam Borowski <kilobyte@angband.pl>,
dsterba@suse.cz, Dmitrii Tcvetkov <demfloro@demfloro.ru>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 0/6] Chunk level degradable check
Date: Thu, 13 Jul 2017 08:12:13 -0400 [thread overview]
Message-ID: <4b993f48-a52e-cda4-fb20-9906aabbc77d@gmail.com> (raw)
In-Reply-To: <20170713010949.jyt24oebfwjngmcz@angband.pl>
On 2017-07-12 21:09, Adam Borowski wrote:
> On Thu, Jul 13, 2017 at 02:50:10AM +0200, David Sterba wrote:
>> On Mon, Jul 10, 2017 at 09:11:50PM +0300, Dmitrii Tcvetkov wrote:
>>> Tested on top of current mainline master (commit
>>> af3c8d98508d37541d4bf57f13a984a7f73a328c). Didn't find any
>>> regressions.
>
> I've retested this yet again. No regressions as well.
Same here, including checking on a number of MIPS, PPC, and ARM variants
in QEMU.
>
>> Thanks for testing.
>>
>> If anybody wants to get their Tested-by in the patches, please let me
>> know, I'll add the tags (can be done until rc6). Your efforts are
>> appreciated so you get the credit in the undying history log of linux
>> kernel.
>
> Heh. Let's not play such games but finally get this patch set in, it's by
> far the biggest problem for multi-device.
Agreed, this should have gone in back when the first version was posted...
next prev parent reply other threads:[~2017-07-13 12:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 5:43 [PATCH v4 0/6] Chunk level degradable check Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 1/6] btrfs: Introduce a function to check if all chunks a OK for degraded rw mount Qu Wenruo
2017-07-14 7:44 ` Nikolay Borisov
2017-07-14 8:19 ` Qu Wenruo
2017-07-18 16:29 ` David Sterba
2017-06-28 5:43 ` [PATCH v4 2/6] btrfs: Do chunk level rw degrade check at mount time Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 3/6] btrfs: Do chunk level degradation check for remount Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 4/6] btrfs: Allow barrier_all_devices to do chunk level device check Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 5/6] btrfs: Cleanup num_tolerated_disk_barrier_failures Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 6/6] btrfs: Enhance missing device kernel message Qu Wenruo
2017-06-28 13:54 ` [PATCH v4 0/6] Chunk level degradable check David Sterba
2017-07-10 18:11 ` Dmitrii Tcvetkov
2017-07-13 0:50 ` David Sterba
2017-07-13 1:09 ` Adam Borowski
2017-07-13 12:12 ` Austin S. Hemmelgarn [this message]
2017-07-12 15:24 ` David Sterba
2017-07-12 23:53 ` Qu Wenruo
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=4b993f48-a52e-cda4-fb20-9906aabbc77d@gmail.com \
--to=ahferroin7@gmail.com \
--cc=demfloro@demfloro.ru \
--cc=dsterba@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/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).