From: james.smart@broadcom.com (James Smart)
Subject: [PATCH rfc v2 09/10] nvme-cli: add --quiet option
Date: Sun, 14 Jul 2019 07:49:14 -0700 [thread overview]
Message-ID: <898fcfa4-e70f-fd0d-0905-cc4af74d4cda@broadcom.com> (raw)
In-Reply-To: <46dcab64-c4f9-74dc-b75c-4f4b8926051d@grimberg.me>
On 7/12/2019 10:35 AM, Sagi Grimberg wrote:
>
> Q is already a short-arg (queue-size). Lets have it 'S' (stand for
> Suppress).
ok...
> Also, when I tested it locally for some reason it did not
> take:
> --
> Jul 12 17:30:00 nvmc systemd[1]: Started NVMf auto-connect scan upon
> nvme discovery controller Events.
> Jul 12 17:30:00 nvmc sh[2767]: Failed to write to /dev/nvme-fabrics:
> Operation already in progress
> Jul 12 17:30:00 nvmc sh[2767]: traddr=192.168.123.1 is already connected
> Jul 12 17:30:00 nvmc kernel: nvme nvme2: creating 4 I/O queues.
> Jul 12 17:30:00 nvmc kernel: nvme nvme2: mapped 4/0/0
> default/read/poll queues.
> Jul 12 17:30:00 nvmc kernel: nvme nvme2: new ctrl: NQN "testnqn2",
> addr 192.168.123.1:8009
> --
>
> Adding print to add_ctrl:
> Jul 12 17:30:00 nvmc sh[2767]: errno 114 quiet 0
>
> When I pass it manually it works, but not from udev... Not sure what
> is going on...
?? I'll check it on my side
next prev parent reply other threads:[~2019-07-14 14:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 0:31 [PATCH rfc v2 00/10] nvme-cli: nvmf auto-connect scripts James Smart
2019-07-12 0:31 ` [PATCH rfc v2 01/10] nvme-cli: ignore arguments that pass in "none" James Smart
2019-07-12 0:31 ` [PATCH rfc v2 02/10] nvme-cli: support persistent connections to a discovery controller James Smart
2019-07-12 0:31 ` [PATCH rfc v2 03/10] nvme-cli: allow discover to address discovery controller by persistent name James Smart
2019-07-12 1:34 ` Minwoo Im
2019-07-12 12:41 ` Hannes Reinecke
2019-07-12 16:37 ` Sagi Grimberg
2019-07-12 0:31 ` [PATCH rfc v2 04/10] nvme-cli: Refactor to create a get_nvme_ctrl_info routine James Smart
2019-07-12 0:50 ` Sagi Grimberg
2019-07-12 6:20 ` Hannes Reinecke
2019-07-12 0:31 ` [PATCH rfc v2 05/10] nvme-cli: extend ctrl_list_item for connect attributes James Smart
2019-07-12 0:47 ` Sagi Grimberg
2019-07-16 0:11 ` James Smart
2019-07-16 1:13 ` Sagi Grimberg
2019-07-12 6:24 ` Hannes Reinecke
2019-07-12 0:31 ` [PATCH rfc v2 06/10] nvme-cli: Add routine to compare ctrl_list_item to connect args James Smart
2019-07-12 0:49 ` Sagi Grimberg
2019-07-12 6:25 ` Hannes Reinecke
2019-07-12 0:31 ` [PATCH rfc v2 07/10] nvme-cli: Add routine to search for controller with specific attributes James Smart
2019-07-12 0:50 ` Sagi Grimberg
2019-07-12 6:28 ` Hannes Reinecke
2019-07-12 0:31 ` [PATCH rfc v2 08/10] nvme-cli: Expand --device argument processing James Smart
2019-07-12 0:51 ` Sagi Grimberg
2019-07-12 14:10 ` Hannes Reinecke
2019-07-12 0:31 ` [PATCH rfc v2 09/10] nvme-cli: add --quiet option James Smart
2019-07-12 17:35 ` Sagi Grimberg
2019-07-14 14:49 ` James Smart [this message]
2019-07-15 23:34 ` James Smart
2019-07-12 0:31 ` [PATCH rfc v2 10/10] nvme-cli: nvmf auto-connect scripts James Smart
2019-07-12 0:42 ` Sagi Grimberg
2019-07-12 17:26 ` Sagi Grimberg
2019-07-14 14:47 ` James Smart
2019-07-15 17:20 ` Sagi Grimberg
2019-07-12 17:55 ` Sagi Grimberg
2019-07-14 14:49 ` James Smart
2019-07-12 17:58 ` Sagi Grimberg
2019-07-14 14:57 ` James Smart
2019-07-15 17:21 ` Sagi Grimberg
2019-07-15 19:04 ` James Smart
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=898fcfa4-e70f-fd0d-0905-cc4af74d4cda@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 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.