From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>,
Hannes Reinecke <hare@kernel.org>, Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet: return 'namespace not ready' for disabled namespaces
Date: Mon, 19 Aug 2024 15:54:44 +0200 [thread overview]
Message-ID: <9e1839fc-5b8f-435f-abde-e8fb1bd9b60d@suse.de> (raw)
In-Reply-To: <dc3d279d-58a9-412b-9cb3-cc51297f65ba@grimberg.me>
On 8/19/24 15:17, Sagi Grimberg wrote:
>
>
>
> On 19/08/2024 15:29, Hannes Reinecke wrote:
>> When a namespace is disabled from configfs returning 'path error'
>> is quite an odd choice; the actual description for that error is:
>> 'The command was not completed as a result of a controller internal
>> error that is specific to the controller processing the command.'
>> Which is not the case here; once disabled the namespace is disabled
>> for the entire subsystem, not just the controller.
>> So return 'namespace not ready' here to clarify the problem.
>
> Hannes, can you explain what this patch is solving?
>
> The reason why this error was selected is because this is a path
> error, which will trigger a host IO failover.
???
This is not a path error.
# echo 0 >
/sys/kernel/config/nvmet/subsystems/<NQN>/namespaces/<NSID>/enable
will disable the namespace for all controllers. Not just the individual
path (as there is not individual path). Failover won't change anything.
Hence this change.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2024-08-19 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 12:29 [PATCH] nvmet: return 'namespace not ready' for disabled namespaces Hannes Reinecke
2024-08-19 13:17 ` Sagi Grimberg
2024-08-19 13:54 ` Hannes Reinecke [this message]
2024-08-19 14:22 ` Sagi Grimberg
2024-08-22 6:56 ` Christoph Hellwig
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=9e1839fc-5b8f-435f-abde-e8fb1bd9b60d@suse.de \
--to=hare@suse.de \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.