From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f47.google.com ([209.85.214.47]:38214 "EHLO mail-it0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753208AbcHONmC (ORCPT ); Mon, 15 Aug 2016 09:42:02 -0400 Received: by mail-it0-f47.google.com with SMTP id n128so7358479ith.1 for ; Mon, 15 Aug 2016 06:42:01 -0700 (PDT) Subject: Re: How to stress test raid6 on 122 disk array To: Martin References: <274e0a56-086f-23c4-7ae9-2b6cb68ec6c8@gmail.com> <71a331cf-b8cf-73f0-74a2-db09a21e5d04@gmail.com> Cc: Chris Murphy , Btrfs BTRFS From: "Austin S. Hemmelgarn" Message-ID: Date: Mon, 15 Aug 2016 09:41:38 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 2016-08-15 09:38, Martin wrote: >> Looking at the kernel log itself, you've got a ton of write errors on >> /dev/sdap. I would suggest checking that particular disk with smartctl, and >> possibly checking the other hardware involved (the storage controller and >> cabling). >> >> I would kind of expect BTRFS to crash with that many write errors regardless >> of what profile is being used, but we really should get better about >> reporting errors to user space in a sane way (making people dig through >> kernel logs to figure out their having issues like this is not particularly >> user friendly). > > Interesting! > > Why does it speak of "device sdq" and /dev/sdap ? > > [337411.703937] BTRFS error (device sdq): bdev /dev/sdap errs: wr > 36973, rd 0, flush 1, corrupt 0, gen 0 > [337411.704658] BTRFS warning (device sdq): lost page write due to IO > error on /dev/sdap > > /dev/sdap doesn't exist. > I'm not quite certain, something in the kernel might have been confused, but it's hard to be sure.