[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <a817431f-276f-4aab-9ff8-c3e397494339@www.fastmail.com>
Date: Thu, 18 Aug 2022 00:18:29 -0400
From: "Chris Murphy" <lists@...orremedies.com>
To: "Ming Lei" <ming.lei@...hat.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>
Subject: Re: stalling IO regression since linux 5.12, through 5.18
On Thu, Aug 18, 2022, at 12:12 AM, Chris Murphy wrote:
> On Wed, Aug 17, 2022, at 11:41 PM, Ming Lei wrote:
>
>> OK, can you post the blk-mq debugfs log after you trigger it on v5.17?
>
> https://drive.google.com/file/d/1n8f66pVLCwQTJ0PMd71EiUZoeTWQk3dB/view?usp=sharing
>
> This time it happened pretty quickly. This log is soon after triple
> digit load and no IO, but not as fully developed as before. The system
> has become entirely unresponsive to new commands, so I have to issue
> sysrq+b - if I let it go too long even that won't work.
OK by the time I clicked send, the system had recovered. That also sometimes happens but then later IO stalls again and won't recover. So I haven't issued sysrq+b on this run yet. Here is a second blk-mq debugfs log...
https://drive.google.com/file/d/1irHcns0qe7e7DJaDfanX8vSiqE1Nj5xl/view?usp=sharing
--
Chris Murphy
Powered by blists - more mailing lists