From: s90752@hotmail.com (Ching-Chiao Chang)
Subject: Whenever running nvme discover command, syslog shows warning messages
Date: Tue, 4 Dec 2018 22:27:26 +0000 [thread overview]
Message-ID: <BN6PR1301MB2001C46B2AA0738A52AEDD6885AF0@BN6PR1301MB2001.namprd13.prod.outlook.com> (raw)
In-Reply-To: <4fb9c4fc-e5ce-2238-fbcf-1fdd6da10e23@broadcom.com>
Hi,
It is not test case, we would like to run nvme discover in loop in an initiator, and whenever there is an NVMe volume can be attached, the the initiator can discover it and connect it automatically.
On the other hand, could I know why do the following logs shows when?running?nvme discover???what do the logs represent?
sqsize 128 > ctrl maxcmd 1, clamping down
new ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery", addr 10.10.0.4:4420
Removing ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery"
Thank you?very much.
From: James Smart <james.smart@broadcom.com>
Sent: Saturday, December 1, 2018 2:48 AM
To: Ching-Chiao Chang; Sagi Grimberg; linux-nvme at lists.infradead.org
Subject: Re: Whenever running nvme discover command, syslog shows warning messages
?
but that's not normal, sounds like a test case.?? I wouldn't want to
lose a debuggable situation in the field because your test case made it
chatty.
On 11/29/2018 6:40 PM, Ching-Chiao Chang wrote:
> The reason I would like to avoid those messages is that when we put the nvme discover command in a loop, it generates a tons of those messages is syslog.
>
>
>
> Thanks.
>
>
> From: Sagi Grimberg <sagi at grimberg.me>
> Sent: Friday, November 30, 2018 9:34 AM
> To: James Smart; Ching-Chiao Chang; linux-nvme at lists.infradead.org
> Subject: Re: Whenever running nvme discover command, syslog shows warning messages
>??
>
>> 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.
> We can filter it out for discovery controllers... I'm pretty indifferent
> about it...
next prev parent reply other threads:[~2018-12-04 22:27 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
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 [this message]
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=BN6PR1301MB2001C46B2AA0738A52AEDD6885AF0@BN6PR1301MB2001.namprd13.prod.outlook.com \
--to=s90752@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.