From: keith.busch@linux.intel.com (Keith Busch)
Subject: How /dev/nvme numbers are allocated/mapped to BDF
Date: Fri, 3 Aug 2018 10:54:11 -0600 [thread overview]
Message-ID: <20180803165411.GA4551@localhost.localdomain> (raw)
In-Reply-To: <097442158bb64b9cbf07cc6e6c25ef1a@ausx13mps321.AMER.DELL.COM>
On Fri, Aug 03, 2018@04:16:16PM +0000, Alex_Gagniuc@Dellteam.com wrote:
> Thanks. I'm fairly convinced I have that patch. I can see by-path links
> for Intel drives, but not the Samasungs.
>
> [root at g-prime mrnuke]# ls /dev/disk/by-path/ |grep nvme
> pci-0000:3f:00.0-nvme-1
> pci-0000:3f:00.0-nvme-1-part1
> pci-0000:b1:00.0-nvme-1
> pci-0000:b1:00.0-nvme-1-part1
>
> [root at g-prime mrnuke]# lspci |grep NVM
> 3f:00.0 Non-Volatile memory controller: Intel Corporation Express Flash NVMe P4500
> 40:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01)
> b1:00.0 Non-Volatile memory controller: Intel Corporation Express Flash NVMe P4600
> b2:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01)
>
>
> [root at g-prime mrnuke]# nvme list
> Node SN Model Namespace Usage Format FW Rev
> ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
> /dev/nvme0n1 PHLF7363029G1P0GGN Dell Express Flash NVMe P4500 1.0TB SFF 1 1.00 TB / 1.00 TB 512 B + 0 B QDV1DP12
> /dev/nvme1n1 PHLE7260008Z3P2EGN Dell Express Flash NVMe P4600 3.2TB SFF 1 3.20 TB / 3.20 TB 512 B + 0 B QDV1DP12
> /dev/nvme2n1 S39YNX0HB00195 Dell Express Flash PM1725a 800GB SFF 1 800.17 GB / 800.17 GB 512 B + 0 B 1.0.4
> /dev/nvme3n1 S39YNX0HB00293 Dell Express Flash PM1725a 800GB SFF 1 800.17 GB / 800.17 GB 512 B + 0 B 1.0.4
The sammy drives do not have compliant serial number. Spec requires
strings are left justified, padding spaces to the right.
Not that it should matter to the by-path symlinks...
Could you attach output from:
udevadm test -a -p $(udevadm info -q path -n /dev/nvme2n1)
next prev parent reply other threads:[~2018-08-03 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 22:09 How /dev/nvme numbers are allocated/mapped to BDF Alex_Gagniuc
2018-08-03 7:18 ` Christoph Hellwig
2018-08-03 14:40 ` Keith Busch
2018-08-03 16:16 ` Alex_Gagniuc
2018-08-03 16:54 ` Keith Busch [this message]
2018-08-03 16:58 ` Johannes Thumshirn
2018-08-03 17:07 ` Keith Busch
2018-08-03 17:20 ` Alex_Gagniuc
2018-08-03 17:40 ` Keith Busch
2018-08-04 8:16 ` Christoph Hellwig
2018-08-05 15:48 ` Alex_Gagniuc
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=20180803165411.GA4551@localhost.localdomain \
--to=keith.busch@linux.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