From: Carlos Carvalho <carlos@fisica.ufpr.br>
To: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 6.5.0rc5 fs hang - ext4? raid?
Date: Tue, 15 Aug 2023 15:21:24 -0300 [thread overview]
Message-ID: <ZNvCJAclBEJf7uUA@fisica.ufpr.br> (raw)
In-Reply-To: <ZNqWfQPTScJDkmpX@gallifrey>
Dr. David Alan Gilbert (dave@treblig.org) wrote on Mon, Aug 14, 2023 at 06:02:53PM -03:
> I'm seeing a few hangs on a fs after upgrading to fedora 39's bleeding
> edge; which is running kernel 6.5.0-0.rc5.20230808git14f9643dc90a.37.fc39.x86_64
> It was always solid prior to that. It seems to trigger on heavy IO
> on this fs.
Good news! No, I didn't forget the smiley... Maybe now the problem has become
sufficiently bad to be visible/solvable...
6.4.* also doesn't run in one of our machines, which has heavy I/O load. The
first symptom is that rsync downloads hang and abort with timeout. 1 or 2
days later the amount of modified pages waiting to go to disk reaches several
GB, as reported by /proc/meminfo, but disks remain idle. Finally reading from
the arrays collapses.
This is just the worst case. Since early 5.* I/O performance has dropped
absurdly. In all our disk servers this is easy to see: just generate lots of
writes quickly (for example expanding a kernel tarball). Using top I see that
kworker starts using 100% cpu but disks stay idle (as seen by dstat or sar). If
you do a sync or umount it takes looooong to reach ~0 modified pages for the
sync or umount to return.
In the server I mentioned above where 6.4.* don't stand the load, which is one
of the largest free software mirrors of the world, even sometimes 6.1
collapses: I/O becomes so slow that service (apache) stops.
The problem gets progressively worse with time after booting. It's hardly
noticeable in the first hour after boot, and easily seen after ~3-4 days of
uptime. The higher the (write) I/O load the faster it appears.
All this is with ext4 and raid6 with >~ 14 disks in the arrays.
I don't have debug info because these are production machines and I only
compile in the kernel the bare minimum essential for operation. It's always
pure kernel.org releases; gcc versions vary, for 6.4* it's gcc-13, for 6.1*
gcc-12 is used, on Debian unstable updated more than 4 times/week.
next prev parent reply other threads:[~2023-08-15 18:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 21:02 Dr. David Alan Gilbert
2023-08-15 0:16 ` Bagas Sanjaya
2023-08-15 0:23 ` Dr. David Alan Gilbert
2023-08-15 1:11 ` Bagas Sanjaya
2023-08-15 11:47 ` Yu Kuai
2023-08-15 12:23 ` Dr. David Alan Gilbert
2023-08-15 12:47 ` Yu Kuai
2023-08-15 12:51 ` Theodore Ts'o
2023-08-15 12:55 ` Dr. David Alan Gilbert
2023-08-15 17:50 ` Dr. David Alan Gilbert
2023-08-16 1:31 ` Dr. David Alan Gilbert
2023-08-16 14:34 ` Jens Axboe
2023-08-16 14:44 ` Dr. David Alan Gilbert
2023-08-16 15:06 ` Dr. David Alan Gilbert
2023-08-16 15:30 ` Jens Axboe
2023-08-28 13:52 ` Bagas Sanjaya
2023-08-28 13:55 ` Jens Axboe
2023-08-28 14:00 ` Dr. David Alan Gilbert
2023-08-28 14:02 ` Bagas Sanjaya
2023-08-28 14:08 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-15 18:21 ` Carlos Carvalho [this message]
2023-08-15 18:52 ` Dr. David Alan Gilbert
2023-08-16 0:43 ` Dr. David Alan Gilbert
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=ZNvCJAclBEJf7uUA@fisica.ufpr.br \
--to=carlos@fisica.ufpr.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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
all inboxes | Powered by JetHome®