linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Ken Long <kelargo1000@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: trying to balance, filesystem keeps going read-only.
Date: Sun, 1 Nov 2015 19:17:30 +0500	[thread overview]
Message-ID: <20151101191730.298dcff4@natsu> (raw)
In-Reply-To: <CAAvdE8T8AzeENxgYDvTTCN7H2RsBZg07mv+KsuPDG7AdLixCxA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

On Sun, 1 Nov 2015 09:07:08 -0500
Ken Long <kelargo1000@gmail.com> wrote:

> Yes, the one drive is that Seagate 8TB drive..
> 
> Smart tools doesn't show anything outrageous or obvious in hardware.
> 
> Is there any other info I can provide to isolate, troubleshoot further?
> 
> I'm not sure how to correlate the dmesg message to a specific drive,
> SATA cable etc..

See this discussion: http://www.spinics.net/lists/linux-btrfs/msg48054.html

My guess is these drives need to do a lot of housekeeping internally,
especially during heavy write load or random writes, and do not reply to the
host machine in time, which translates into those "frozen [...] failed
command: WRITE FPDMA QUEUED" failures.

I did not follow the issue closely enough to know if there's a solution yet, or
even if this is specific to Btrfs or to GNU/Linux in general. Maybe your best
bet would be to avoid using that drive in your Btrfs array altogether for the
time being.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-11-01 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 11:24 trying to balance, filesystem keeps going read-only Ken Long
2015-11-01 12:34 ` Hugo Mills
2015-11-01 13:48 ` Roman Mamedov
2015-11-01 14:07   ` Ken Long
2015-11-01 14:17     ` Roman Mamedov [this message]
2015-11-01 14:33       ` Ken Long
2015-11-02 12:36         ` Austin S Hemmelgarn

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=20151101191730.298dcff4@natsu \
    --to=rm@romanrm.net \
    --cc=kelargo1000@gmail.com \
    --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).