From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "alan.adamson@oracle.com" <alan.adamson@oracle.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: debugfs message during creation of the NVMeOf controller
Date: Sun, 26 Mar 2023 23:44:09 +0000 [thread overview]
Message-ID: <c8c21fdb-ec06-2b4a-a42a-b4c8c34df673@nvidia.com> (raw)
In-Reply-To: <8ee89033-d454-072a-6fe2-e2bf24ece2fc@oracle.com>
On 3/24/23 15:34, alan.adamson@oracle.com wrote:
>
> On 3/23/23 1:18 AM, Chaitanya Kulkarni wrote:
>> Hi everyone,
>>
>> Whenever I create NVMeOF target controller using nvme-loop
>> transport I'm getting following message:-
>>
>> [18318.052193] debugfs: Directory 'nvme1' with parent '/' already
>> present!
>> [18318.053164] nvme1: failed to create debugfs attr
>> [18318.053239] nvmet: creating nvm controller 1 for subsystem testnqn
>> for NQN
>> nqn.2014-08.org.nvmexpress:uuid:bb0a23ee-0be3-4285-8d8a-b47fcad11fe1.
>> [18318.053369] nvme nvme1: creating 48 I/O queues.
>> [18318.058812] nvme nvme1: new ctrl: "testnqn"
>>
>> It is certainly coming from
>> host/fault_inject.c:nvme_fault_inject_init().
>>
>> any idea about this ?
>>
> I may have seen this before, but I can't seem to reproduce it. Can you
>
> provide the script the creates the targets?
>
> Alan
>
with latest pull on the nvme-6.4 the message is gone.
It was coming from blktests.
-ck
next prev parent reply other threads:[~2023-03-26 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 8:18 debugfs message during creation of the NVMeOf controller Chaitanya Kulkarni
2023-03-24 22:34 ` alan.adamson
2023-03-26 23:44 ` Chaitanya Kulkarni [this message]
2023-03-26 23:48 ` Chaitanya Kulkarni
2023-03-27 5:27 ` Chaitanya Kulkarni
2023-03-27 17:44 ` [PATCH] nvme: fix error handling in nvme_init_ctrl() Akinobu Mita
2023-03-27 18:23 ` Chaitanya Kulkarni
2023-03-27 22:12 ` alan.adamson
2023-04-25 8:31 ` debugfs message during creation of the NVMeOf controller Yi Zhang
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=c8c21fdb-ec06-2b4a-a42a-b4c8c34df673@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=alan.adamson@oracle.com \
--cc=linux-nvme@lists.infradead.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