linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "Zhu, YifeiX" <yifeix.zhu@intel.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: "Li, Philip" <philip.li@intel.com>,
	"Ma, XinjianX" <xinjianx.ma@intel.com>
Subject: Re: blktests nvme testcase error
Date: Tue, 7 Sep 2021 07:05:32 +0000	[thread overview]
Message-ID: <b26b4808-fd69-04fe-dbd4-fa45fa75b5fe@nvidia.com> (raw)
In-Reply-To: <DM6PR11MB39327C5E42F053888DA37BDB84D29@DM6PR11MB3932.namprd11.prod.outlook.com>


> CODE:
>      221 _create_nvmet_ns() {
>      222         local nvmet_subsystem="$1"
>      223         local nsid="$2"
>      224         local blkdev="$3"
>      225         local uuid="00000000-0000-0000-0000-000000000000"
>      226         local subsys_path="${NVMET_CFS}/subsystems/${nvmet_subsystem}"
>      227         local ns_path="${subsys_path}/namespaces/${nsid}"
>      228
>      229         if [[ $# -eq 4 ]]; then
>      230                 uuid="$4"
>      231         fi
>      232
>      233         mkdir "${ns_path}"
>      234         printf "%s" "${blkdev}" > "${ns_path}/device_path"
>      235         printf "%s" "${uuid}" > "${ns_path}/device_uuid"
>      236         printf 1 > "${ns_path}/enable"
>      237 }
> 

You should be able to get the error in the dmsg, please share that output..

  reply	other threads:[~2021-09-07  7:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  6:27 blktests nvme testcase error Zhu, YifeiX
2021-09-07  7:05 ` Chaitanya Kulkarni [this message]
2021-09-15  7:47   ` Zhu, YifeiX

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=b26b4808-fd69-04fe-dbd4-fa45fa75b5fe@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=philip.li@intel.com \
    --cc=xinjianx.ma@intel.com \
    --cc=yifeix.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).