[
https://issues.apache.org/jira/browse/LUCENE-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602914#comment-14602914
]
Steve Rowe commented on LUCENE-6614:
------------------------------------
bq. I think Steve Rowe also has an NVME drive ...
Yes, I do.
In fact, Debian 8 failed to install properly because of the new NVMe device
naming scheme, and I had to patch grub-installer and initramfs-tools to deal
with it - see the bug reports I created:
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147] and
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785149].
In the grub-installer script's device-to-disk method, which is a longish regex
to strip off suffixes based on disk prefixes, there is a comment "# This should
probably be rewritten using udevadm or similar."
On my system, {{udevadm info /dev/nvme0n1p2}} (the root mount point) says:
{noformat}
P: /devices/pci0000:00/0000:00:02.0/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p2
N: nvme0n1p2
S: disk/by-partuuid/7c4cb587-74ba-471f-8a6d-8b5d94c3c86b
S: disk/by-uuid/9954878e-5783-4f4b-bca3-55d689f221da
E: DEVLINKS=/dev/disk/by-partuuid/7c4cb587-74ba-471f-8a6d-8b5d94c3c86b
/dev/disk/by-uuid/9954878e-5783-4f4b-bca3-55d689f221da
E: DEVNAME=/dev/nvme0n1p2
E:
DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p2
E: DEVTYPE=partition
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=9954878e-5783-4f4b-bca3-55d689f221da
E: ID_FS_UUID_ENC=9954878e-5783-4f4b-bca3-55d689f221da
E: ID_FS_VERSION=1.0
E: ID_PART_ENTRY_DISK=259:0
E: ID_PART_ENTRY_NUMBER=2
E: ID_PART_ENTRY_OFFSET=1050624
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_SIZE=646338560
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_UUID=7c4cb587-74ba-471f-8a6d-8b5d94c3c86b
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=c454b1a9-e191-4d93-a9af-db80b81485a8
E: MAJOR=259
E: MINOR=2
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=11060677
{noformat}
Similarly, taking the {{/by-uuid/}} path from {{E: DEVLINKS}} above, {{udevadm
info /dev/disk/by-uuid/9954878e-5783-4f4b-bca3-55d68}} says:
{noformat}
P: /devices/pci0000:00/0000:00:02.0/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p2
N: nvme0n1p2
S: disk/by-partuuid/7c4cb587-74ba-471f-8a6d-8b5d94c3c86b
S: disk/by-uuid/9954878e-5783-4f4b-bca3-55d689f221da
E: DEVLINKS=/dev/disk/by-partuuid/7c4cb587-74ba-471f-8a6d-8b5d94c3c86b
/dev/disk/by-uuid/9954878e-5783-4f4b-bca3-55d689f221da
E: DEVNAME=/dev/nvme0n1p2
E:
DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p2
E: DEVTYPE=partition
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=9954878e-5783-4f4b-bca3-55d689f221da
E: ID_FS_UUID_ENC=9954878e-5783-4f4b-bca3-55d689f221da
E: ID_FS_VERSION=1.0
E: ID_PART_ENTRY_DISK=259:0
E: ID_PART_ENTRY_NUMBER=2
E: ID_PART_ENTRY_OFFSET=1050624
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_SIZE=646338560
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_UUID=7c4cb587-74ba-471f-8a6d-8b5d94c3c86b
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=c454b1a9-e191-4d93-a9af-db80b81485a8
E: MAJOR=259
E: MINOR=2
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=11060677
{noformat}
In both cases, {{E: DEVPATH}} has the correct block device name as the
second-to-last path segment.
> IOUtils.spins doesn't work for drives NVMe drives
> -------------------------------------------------
>
> Key: LUCENE-6614
> URL: https://issues.apache.org/jira/browse/LUCENE-6614
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Uwe Schindler
> Priority: Minor
> Fix For: 5.3, Trunk
>
> Attachments: LUCENE-6614.patch
>
>
> NVMe is the faster (than AHCI) protocol for newer SSDs that plug into the
> PCIE bus.
> I just built a new beast box with one of these drives, and the partition is
> named {{/dev/nvme0n1p1}} while the device is {{/dev/nvme0n1}} by Linux - this
> also appears in /sys/block with rotational=0.
> I think [~steve_rowe] also has an NVME drive ...
> [~thetaphi] (who got the box working for me: thank you!!!) has ideas on how
> to fix it!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
