From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f51.google.com ([209.85.218.51]:32838 "EHLO mail-oi0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751231AbcFYVw3 (ORCPT ); Sat, 25 Jun 2016 17:52:29 -0400 Received: by mail-oi0-f51.google.com with SMTP id u201so158027625oie.0 for ; Sat, 25 Jun 2016 14:52:29 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20160620204049.GA1986@hungrycats.org> <20160621015559.GM15597@hungrycats.org> <20160622203504.GQ15597@hungrycats.org> <5790aea9-0976-1742-7d1b-79dbe44008c3@inwind.it> <20160624014752.GB14667@hungrycats.org> <576CB0DA.6030409@gmail.com> <20160624085014.GH3325@carfax.org.uk> <576D6C0A.7070502@gmail.com> From: Chris Murphy Date: Sat, 25 Jun 2016 15:52:26 -0600 Message-ID: Subject: Re: Adventures in btrfs raid5 disk recovery To: Chris Murphy Cc: "Austin S. Hemmelgarn" , Andrei Borzenkov , Hugo Mills , Zygo Blaxell , kreijack@inwind.it, Roman Mamedov , Btrfs BTRFS Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: Interestingly enough, so far I'm finding with full stripe writes, i.e. 3x raid5, exactly 128KiB data writes, devid 3 is always parity. This is raid4. So...I wonder if some of these slow cases end up with a bunch of stripes that are effectively raid4-like, and have a lot of parity overwrites, which is where raid4 suffers due to disk contention. Totally speculative as the sample size is too small and distinctly non-random. Chris Murphy