From: james.smart@broadcom.com (James Smart)
Subject: Whenever running nvme discover command, syslog shows warning messages
Date: Thu, 29 Nov 2018 09:01:47 -0800 [thread overview]
Message-ID: <bdd5f3c7-8173-dd63-3a47-df87a9c2d14c@broadcom.com> (raw)
In-Reply-To: <CY4PR1301MB2008564EA917C4FE4D63298585D20@CY4PR1301MB2008.namprd13.prod.outlook.com>
On 11/28/2018 4:50 PM, Ching-Chiao Chang wrote:
> Hi,
>
> Whenever running nvme discover command, i.e., nvme discover --transport=rdma --traddr=10.10.0.4, syslog shows the following messages,
> Nov 27 15:24:30 initiator-xxx kernel: [55897.822948] nvme nvme1: sqsize 128 > ctrl maxcmd 1, clamping down
> Nov 27 15:24:30 initiator-xxx kernel: [55897.822956] nvme nvme1: new ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery", addr 10.10.0.4:4420
> Nov 27 15:24:30 initiator-xxx kernel: [55897.823213] nvme nvme1: Removing ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery"
> ...
> I was wondering if there is any way to avoid these warning messages?
>
> OS: Ubuntu 16.04.5
> Kernel: 4.18.5-041805-generic
> nvme version 1.6.120.g5c8a
>
> Thanks.
> Andy
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
no there's not - currently.
I find them worthwhile to see, as it hints at what the admin or
scripting is doing, as well as giving hints on when nvme? names may be
reallocated. I would not remove them for normal storage controllers.
Perhaps a discovery controller could be filtered out, but I still find
it useful.
-- james
next prev parent reply other threads:[~2018-11-29 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 0:50 Whenever running nvme discover command, syslog shows warning messages Ching-Chiao Chang
2018-11-29 17:01 ` James Smart [this message]
2018-11-30 1:34 ` Sagi Grimberg
2018-11-30 2:40 ` Ching-Chiao Chang
2018-11-30 18:48 ` James Smart
2018-12-04 22:27 ` Ching-Chiao Chang
2018-12-05 1:25 ` James Smart
2018-12-11 17:30 ` Ching-Chiao Chang
2018-12-05 15:43 ` Keith Busch
2018-12-05 20:25 ` Sagi Grimberg
2018-12-05 20:41 ` Keith Busch
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=bdd5f3c7-8173-dd63-3a47-df87a9c2d14c@broadcom.com \
--to=james.smart@broadcom.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