linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Martin <rc6encrypted@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: How to stress test raid6 on 122 disk array
Date: Mon, 15 Aug 2016 09:41:38 -0400	[thread overview]
Message-ID: <f7cdcafc-665e-bc8f-6414-c16c7f42ffe3@gmail.com> (raw)
In-Reply-To: <CAGQ70YeK3ZRqL6XgnqQnb4KwGyiOhG5Oavjhu6_L+VhE+uO2sQ@mail.gmail.com>

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.

  reply	other threads:[~2016-08-15 13:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 17:43 How to stress test raid6 on 122 disk array Martin
2016-08-04 19:05 ` Austin S. Hemmelgarn
2016-08-04 20:01   ` Chris Murphy
2016-08-04 20:51     ` Martin
2016-08-04 21:12       ` Chris Murphy
2016-08-04 22:19         ` Martin
2016-08-05 10:15           ` Erkki Seppala
2016-08-15 12:19             ` Martin
2016-08-15 12:38               ` Austin S. Hemmelgarn
2016-08-15 13:39                 ` Martin
2016-08-15 13:47                   ` Austin S. Hemmelgarn
2016-08-05 11:39         ` Austin S. Hemmelgarn
2016-08-15 12:19           ` Martin
2016-08-15 12:44             ` Austin S. Hemmelgarn
2016-08-15 13:38               ` Martin
2016-08-15 13:41                 ` Austin S. Hemmelgarn [this message]
2016-08-15 13:43                 ` Chris Murphy
2016-08-15 13:40             ` Chris Murphy

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=f7cdcafc-665e-bc8f-6414-c16c7f42ffe3@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=rc6encrypted@gmail.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).