From: Christoph Hellwig <hch@infradead.org>
To: Meng Wang <meng@hcdatainc.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Keith Busch <kbusch@kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: kernel panics when hot removing U.2 nvme disk
Date: Thu, 24 Sep 2020 07:14:28 +0100 [thread overview]
Message-ID: <20200924061428.GA27289@infradead.org> (raw)
In-Reply-To: <BYAPR10MB245671198E40D4F44B2365C1CB390@BYAPR10MB2456.namprd10.prod.outlook.com>
On Thu, Sep 24, 2020 at 05:47:12AM +0000, Meng Wang wrote:
> Thanks for the info. Is it a problem solely for ext4 + nvme combination? If we change file system or use SATA drive, will the problem get workaround?
This will be called for all removals. I think the root cause probably
is in ext4 where the evict_inode method doesn't properly deal with
non available storage.
prev parent reply other threads:[~2020-09-24 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR10MB24561C62C45813B7092E346BCB3F0@BYAPR10MB2456.namprd10.prod.outlook.com>
2020-09-19 1:44 ` kernel panics when hot removing U.2 nvme disk Keith Busch
2020-09-23 20:40 ` Meng Wang
2020-09-24 5:12 ` Christoph Hellwig
2020-09-24 5:47 ` Meng Wang
2020-09-24 6:14 ` Christoph Hellwig [this message]
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=20200924061428.GA27289@infradead.org \
--to=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=meng@hcdatainc.com \
/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;
as well as URLs for NNTP newsgroup(s).