[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFj5m9+6Vj3NdSg_n3nw1icscY1qr9f9SOvkWYyqpEtFBb_-1g@mail.gmail.com>
Date: Wed, 17 Aug 2022 20:06:51 +0800
From: Ming Lei <ming.lei@...hat.com>
To: Chris Murphy <lists@...orremedies.com>
Cc: Nikolay Borisov <nborisov@...e.com>, Jens Axboe <axboe@...nel.dk>,
Jan Kara <jack@...e.cz>,
Paolo Valente <paolo.valente@...aro.org>,
Btrfs BTRFS <linux-btrfs@...r.kernel.org>,
Linux-RAID <linux-raid@...r.kernel.org>,
linux-block <linux-block@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Josef Bacik <josef@...icpanda.com>,
Ming Lei <ming.lei@...hat.com>
Subject: Re: stalling IO regression since linux 5.12, through 5.18
Hello Chris,
On Tue, Aug 16, 2022 at 11:35 PM Chris Murphy <lists@...orremedies.com> wrote:
>
>
>
...
>
> I already reported on that: always happens with bfq within an hour or less. Doesn't happen with mq-deadline for ~25+ hours. Does happen with bfq with the above patches removed. Does happen with cgroup.disabled=io set.
>
> Sounds to me like it's something bfq depends on and is somehow becoming perturbed in a way that mq-deadline does not, and has changed between 5.11 and 5.12. I have no idea what's under bfq that matches this description.
>
blk-mq debugfs log is usually helpful for io stall issue, care to post
the blk-mq debugfs log:
(cd /sys/kernel/debug/block/$disk && find . -type f -exec grep -aH . {} \;)
Thanks,
Ming
Powered by blists - more mailing lists