From: Chris Murphy <lists@colorremedies.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Carlos Maiolino <cmaiolino@redhat.com>,
xfs list <linux-xfs@vger.kernel.org>
Subject: Re: Tasks blocking forever with XFS stack traces
Date: Thu, 7 Nov 2019 00:12:40 +0000 [thread overview]
Message-ID: <CAJCQCtQyVNCe7_A4Z743_esvSkbn9LVxUmFV_hAv2rk8s5dkfg@mail.gmail.com> (raw)
In-Reply-To: <CALjAwxiMqjfBX3tZJv3MqMQ776v1aNcwme0B-AuhmEgMNUqgMw@mail.gmail.com>
On Tue, Nov 5, 2019 at 2:13 PM Sitsofe Wheeler <sitsofe@gmail.com> wrote:
>
> My understanding is that the md "chunk size" is 64k so basically
> you're saying the sectsz should have been manually set to be as big as
> possible at mkfs time? I never realised this never happened by default
> (I see the sunit seems to be correct given the block size of 4096 but
> I'm unsure about swidth)...
Check with
# mdadm -E /dev/sdXY
Chunk size depends on the version of mdadm at the time of creation.
It's been a while since 512KiB was the default, leading to rather
large full stripe write size, and a lot of RMW if a significant number
of writes aren't full stripe writes.
--
Chris Murphy
next prev parent reply other threads:[~2019-11-07 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 7:27 Tasks blocking forever with XFS stack traces Sitsofe Wheeler
2019-11-05 8:54 ` Carlos Maiolino
2019-11-05 9:32 ` Sitsofe Wheeler
2019-11-05 10:36 ` Carlos Maiolino
2019-11-05 11:58 ` Carlos Maiolino
2019-11-05 14:12 ` Sitsofe Wheeler
2019-11-05 16:09 ` Carlos Maiolino
2019-11-07 0:12 ` Chris Murphy [this message]
2019-11-13 10:04 ` Sitsofe Wheeler
2020-12-23 8:45 ` Sitsofe Wheeler
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=CAJCQCtQyVNCe7_A4Z743_esvSkbn9LVxUmFV_hAv2rk8s5dkfg@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=cmaiolino@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sitsofe@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).