Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: wenxiong@linux.vnet.ibm.com (wenxiong)
Subject: NVMe disks are not available with lsblk
Date: Thu, 15 Feb 2018 15:35:17 -0600	[thread overview]
Message-ID: <42015a1d2e21bea1bd38227ba3d555af@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180215074425.eiqgxjc5kci2u3zv@linux-x5ow.site>

On 2018-02-15 01:44, Johannes Thumshirn wrote:
> On Wed, Feb 14, 2018@10:40:01AM -0600, wenxiong wrote:
>> Hi All,
>> 
>> Somehow with CONFIG_NVME_MULTIPATH enable(4.16.0-rc1), one of my NVME 
>> device
>> is not showed up with lsblk command.
>> 
>> 
>> I am not familiar with CONFIG_NVME_MULTIPATH enable. I tried to enable
>> multipath in system but still not show up.
>> 
>> For example,/dev/nvme1 device is showed up in nvme list but not with 
>> lsblk.
>> 
>> Anyone saw the similar issue? Any suggestion for debugging this issue?
> 
> Can you chec if you have a this commit:
> https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d51f05bfecb299a830897106460bf395be440c0a
> for util-linux?
> 
> Byte,
> 	Johannes

Hi John,

Thanks! I will try it.

I found an interesting thing today. I have two NVME devices(difference 
vendors) in my system.

With CONFIG_NVME_MULTIPATH enable(4.16-rc1),

linux-r4t8:/sys/block # ls -l
total 0
lrwxrwxrwx 1 root root 0 Feb 15 10:22 nvme0n1 -> 
../devices/pci001e:90/001e:90:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx 1 root root 0 Feb 15 10:22 nvme1c33n1 -> 
../devices/pci001c:70/001c:70:00.0/nvme/nvme1/nvme1c33n1
lrwxrwxrwx 1 root root 0 Feb 15 10:22 nvme1n1 -> 
../devices/virtual/nvme-subsystem/nvme-subsys1/nvme1n1
lrwxrwxrwx 1 root root 0 Feb 15 10:22 sda -> 
../devices/vio/30000003/host0/target0:0:1/0:0:1:0/block/sda

/dev/nvme1n1 is not showed up in lsblk. We really didn't see nvme1n1 in 
/sys/block but we saw nvme1c33n1. Probably I need to understand more 
about NVME_MULTIPATH. who may have documentation for NVME_MULTIPATH?


Without CONFIG_NVME_MULTIPATH disablb(4.16-rc1),

linux-r4t8:/sys/block # ls -ltr
total 0
lrwxrwxrwx 1 root root 0 Feb 15 15:14 nvme1n1 -> 
../devices/pci001c:70/001c:70:00.0/nvme/nvme1/nvme1n1
lrwxrwxrwx 1 root root 0 Feb 15 15:14 sda -> 
../devices/vio/30000003/host0/target0:0:1/0:0:1:0/block/sda
lrwxrwxrwx 1 root root 0 Feb 15 15:14 nvme0n1 -> 
../devices/pci001e:90/001e:90:00.0/nvme/nvme0/nvme0n1

Thanks,
Wendy

      reply	other threads:[~2018-02-15 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 16:40 NVMe disks are not available with lsblk wenxiong
2018-02-15  7:44 ` Johannes Thumshirn
2018-02-15 21:35   ` wenxiong [this message]

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=42015a1d2e21bea1bd38227ba3d555af@linux.vnet.ibm.com \
    --to=wenxiong@linux.vnet.ibm.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