Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-36391

nvme telemetry-log /dev/nvme0 --output-file=telemetry_log.bin failed with "ERROR: get_telemetry_log: : write failed with error : Bad address"

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • rhel-9.5
    • nvme-cli
    • None
    • None
    • None
    • rhel-sst-storage-io
    • ssg_filesystems_storage_and_HA
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      What were you trying to do that didn't work?

      Please provide the package NVR for which bug is seen:

      libnvme-1.9-1.el9.x86_64
      nvme-cli-2.9.1-2.el9.x86_64

      How reproducible:

      100% on Dell Express Flash PM1725a 1.6TB AIC
      And cannot be reproduced with 
      Dell Ent NVMe v2 AGN RI U.2 1.92TB
      Dell Ent NVMe CM6 RI 1.92TB
      Dell Ent NVMe P5500 RI U.2 1.92TB

      Steps to reproduce

      [root@rdma-perf-06 ~]# nvme list
      Node Generic SN Model Namespace Usage Format FW Rev
      --------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
      /dev/nvme0n1 /dev/ng0n1 S39WNA0K400654 Dell Express Flash PM1725a 1.6TB AIC 0x1 1.60 TB / 1.60 TB 512 B + 0 B 1.2.0
      /dev/nvme1n1 /dev/ng1n1 S39WNA0K201139 Dell Express Flash PM1725a 1.6TB AIC 0x1 1.60 TB / 1.60 TB 512 B + 0 B 1.2.0
      [root@rdma-perf-06 ~]# nvme telemetry-log /dev/nvme0 --output-file=telemetry_log.bin
      ERROR: get_telemetry_log: : write failed with error : Bad address
       

      Expected results

      Actual results

      Cannot reproduce this issue with nvme-cli 1.8

              mlombard@redhat.com Maurizio Lombardi
              yizhan@redhat.com Yi Zhang
              Maurizio Lombardi Maurizio Lombardi
              Yi Zhang Yi Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: