[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YOQYKn+POVR2g/h1@T590>
Date: Tue, 6 Jul 2021 16:45:30 +0800
From: Ming Lei <ming.lei@...hat.com>
To: Daniel Wagner <dwagner@...e.de>
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
James Smart <james.smart@...adcom.com>,
Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Sagi Grimberg <sagi@...mberg.me>
Subject: Re: [PATCH 2/2] nvme-fc: Wait with a timeout for queue to freeze
On Tue, Jul 06, 2021 at 10:10:10AM +0200, Daniel Wagner wrote:
> On Tue, Jul 06, 2021 at 03:29:11PM +0800, Ming Lei wrote:
> > > and this seems to confirm, no I/O in flight.
> >
> > What is the output of the following command after the hang is triggered?
> >
> > (cd /sys/kernel/debug/block/nvme0n1 && find . -type f -exec grep -aH . {} \;)
> >
> > Suppose the hang disk is nvme0n1.
>
> see attachement
>
> > No, percpu_ref_is_zero() is fine to be called in atomic mode.
>
> Okay, that is what I hoped for :)
> /sys/kernel/debug/block/nvme0c0n1# find . -type f -exec grep -aH . {} \;
It is the mpath device's debugfs, what is output for the nvmef's
debugfs?
Thanks,
Ming
Powered by blists - more mailing lists