From: "Darrick J. Wong" <djwong@kernel.org>
To: "Eugene K." <eugene@railglorg.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS writing issue
Date: Tue, 11 Jul 2023 08:42:54 -0700 [thread overview]
Message-ID: <20230711154254.GC108251@frogsfrogsfrogs> (raw)
In-Reply-To: <583703ce-1515-a436-1f34-3386150a03c2@railglorg.net>
On Tue, Jul 11, 2023 at 05:31:13PM +0200, Eugene K. wrote:
> Hello.
>
> During investigation of flapping performance problem, it was detected that
> once a process writes big amount of data in a row, the filesystem focus on
> this writing and no other process can perform any IO on this filesystem.
>
> We have noticed huge %iowait on software raid1 (mdraid) that runs on 2 SSD
> drives - on every attempt to write more than 1GB.
>
> The issue happens on any server running 6.4.2, 6.4.0, 6.3.3, 6.2.12 kernel.
> Upon investigating and testing it appeared that server IO performance can be
> completely killed with a single command:
>
> #cat /dev/zero > ./removeme
>
> assuming the ~/removeme file resides on rootfs and rootfs is XFS.
>
> While running this, the server becomes so unresponsive that after ~15
> seconds it's not even possible to login via ssh!
>
> We did reproduce this on every machine with XFS as rootfs running mentioned
> kernels. However, when we converted rootfs from XFS to EXT4(and btrfs), the
> problem disappeared - with the same OS, same kernel binary, same hardware,
> just using ext4 or btrfs instead of xfs.
So use ext4.
--D
> Note. During the hang and being unresponsive, SSD drives are writing data at
> expected performance. Just all the processes except the writing one hang.
>
>
next prev parent reply other threads:[~2023-07-11 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 15:31 XFS writing issue Eugene K.
2023-07-11 15:42 ` Darrick J. Wong [this message]
2023-07-11 23:11 ` Dave Chinner
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=20230711154254.GC108251@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=eugene@railglorg.net \
--cc=linux-xfs@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