linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Ruijter <mruijter@primelogic.nl>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: Exporting NVMe-oF devices read-only enforced on export from the NVMe-oF target.
Date: Wed, 30 Sep 2020 07:38:49 +0000	[thread overview]
Message-ID: <04159F18-52B6-47B2-BF69-E1FD6B67E8A0@primelogic.nl> (raw)
In-Reply-To: <BYAPR04MB4965DEBF8F5F06FC026B502786330@BYAPR04MB4965.namprd04.prod.outlook.com>

Hi Chaitanya,

Let me explain my use case. Since I think we having different things in mind.
You are suggesting to use nvme cli to set an nvme drive namespace to readonly and export it readonly using the NVMe target driver?
This will certainly work, I agree.

In my case let's assume I have a raid device /dev/mdX that I want to export readonly to an initiator. I am unable to run any command on the initiator.
The target should export the device in such a way that the initiator can never accidentally write to it.

I fail to understand how nvme cli NVME_NS_WRITE_PROTECT can help me in this use case?

Thanks,

--Mark


Op 30-09-20 02:29 heeft Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com> geschreven:

    On 9/29/20 04:35, Mark Ruijter wrote:
    > Unless I am mistaken the NVMe-oF target driver does currently not support to export a device read-only from the target system.
    > For exporting readonly snapshot devices I am currently using the attached patch.
    
    It does, have you tried using nvme cli with NVME_NS_WRITE_PROTECT feature ?
    
    we have both host and core patched for read-only mode, if you find any bug
    
    please let me know.
    
    

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-09-30  7:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 11:34 Exporting NVMe-oF devices read-only enforced on export from the NVMe-oF target Mark Ruijter
2020-09-30  0:28 ` Chaitanya Kulkarni
2020-09-30  7:38   ` Mark Ruijter [this message]
2020-10-01  1:41     ` Chaitanya Kulkarni
2020-10-09  0:24   ` Sagi Grimberg
     [not found]     ` <BYAPR04MB496559D7BD43F180E366D91A86080@BYAPR04MB4965.namprd04.prod.outlook.com>
2020-10-09  7:57       ` Sagi Grimberg

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=04159F18-52B6-47B2-BF69-E1FD6B67E8A0@primelogic.nl \
    --to=mruijter@primelogic.nl \
    --cc=Chaitanya.Kulkarni@wdc.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;
as well as URLs for NNTP newsgroup(s).