From: greg@storageio.com (Greg Schulz)
Subject: Problems writing to intel P3700 NVMe drive
Date: Wed, 27 May 2015 18:05:07 -0500 [thread overview]
Message-ID: <00cd01d098d1$94047010$bc0d5030$@storageio.com> (raw)
In-Reply-To: <CAFMq3wE7PzKs=dYxxUhFsHeTkR0CT8mh6NVfrk-9mKxdisoDTg@mail.gmail.com>
Thanks for the follow-up and extra info, I have 3700s running on x86/64 Ubuntu 14.04 and working fine.
I did update the drivers from the Intel site even though they were already in the 14.04 kernel when I was troubel shooting something else.
What happens if you do a dd if=/dev/null of=/dev/nvme0n1 bs=512 count=1000000 conv=notrunc
Cheers gs
-----Original Message-----
From: Linux-nvme [mailto:linux-nvme-bounces@lists.infradead.org] On Behalf Of Pavilion Storage
Sent: Wednesday, May 27, 2015 5:41 PM
To: greg at storageio.com
Cc: linux-nvme at lists.infradead.org
Subject: Re: Problems writing to intel P3700 NVMe drive
Greg,
I am running this on Linux (Ubuntu/3.12) and I am accessing the raw device (/dev/nvme1).
I have tried accessing with dd, nvme-cli and fio Thx Kishore
On Wed, May 27, 2015@3:34 PM, Greg Schulz <greg@storageio.com> wrote:
> I may have missed it somewhere, what OS (and version) are you using?
> Also are you accessing the nvme device e.g. /dev/nvme0n1 raw or via
> partition or filesystem?
> Gs
>
>
> Greg Schulz | Sr. Advisory Analyst | greg at storageio.com Phone
> 651-275-1563 | twitter @storageio | blog www.storageioblog.com
> Server StorageIO and UnlimitedIO LLC aka StorageIO |
> www.storageio.com
>
> Author of the books:
> Cloud and Virtual Data Storage Network (CRC Press & Intel Recommended
> Reading List) The Green and Virtual Data Center (CRC Press & Intel
> Recommended Reading List) Resilient Storage Networks ? Designing
> Flexible Scalable Data Infrastructures (Elsevier)
>
> The information contained in this email and any attachments is
> confidential and may be legally privileged and or confidential. If you
> are not the intended recipient then you must not use, disseminate,
> distribute copy or in any other way use, the information contained in this email or attachments.
> If you receive this email in error, destroy it immediately and contact
> us. Thank you.
>
> -----Original Message-----
> From: Linux-nvme [mailto:linux-nvme-bounces at lists.infradead.org] On
> Behalf Of Pavilion Storage
> Sent: Wednesday, May 27, 2015 4:30 PM
> To: linux-nvme at lists.infradead.org
> Subject: Problems writing to intel P3700 NVMe drive
>
> I am having problems with writing to an intel P3700 NVMe drive on a
> ARM based platform and I would appreciate any help in debugging this problem.
> Here are my experiments and observations so far:
>
> - The drive is usable for read operations and I can run fio
> (randread,
> etc) but I cannot write to it.
> - Other manufacturer's NVMe drive can be inserted into this
> platform and I can write to it
> - I can insert the intel P3700 into an x86 host and I can perform
> write operations
> - I have tried using the nvme-cli
> (https://github.com/linux-nvme/nvme-cli) tool and have read the error
> codes from read. It just shows 'WRITE_FAULT' which is not very helpful.
> - I have looked at the SmartLog reports and the 'Critical Warning'
> is 0, i.e. the device is not in Read-Only mode
> - I have updated the firmware using the intel SSD-DataCenterTool
> and updated the firmware on the drive the latest available version.
> The updated drive works fine on x86 platform.
>
> I think there is some combination of the platform and drive that is
> causing the problem. Can anyone offer pointers on how to debug this?
>
> Thx
> Kishore
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
_______________________________________________
Linux-nvme mailing list
Linux-nvme at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2015-05-27 23:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:30 Problems writing to intel P3700 NVMe drive Pavilion Storage
2015-05-27 22:34 ` Greg Schulz
2015-05-27 22:40 ` Pavilion Storage
2015-05-27 23:05 ` Greg Schulz [this message]
2015-05-27 23:53 ` Pavilion Storage
2015-05-28 0:24 ` j cagle
2015-05-28 0:37 ` Pavilion Storage
2015-05-28 0:46 ` Pavilion Storage
[not found] ` <CA+At7pWf6Ge3pc7=aeiqz=iWxtYJSPVdM_W2XW9pL4d22q432Q@mail.gmail.com>
[not found] ` <000a01d098ee$b52ce0c0$1f86a240$@storageio.com>
2015-05-28 20:53 ` Pavilion Storage
2015-05-28 21:03 ` Keith Busch
2015-05-28 21:19 ` Pavilion Storage
2015-05-28 21:31 ` Keith Busch
2015-06-03 20:10 ` Keith Busch
2015-06-03 20:10 ` Keith Busch
2015-06-03 20:20 ` Bjorn Helgaas
2015-06-03 20:20 ` Bjorn Helgaas
2015-06-03 21:37 ` Keith Busch
2015-06-03 21:37 ` Keith Busch
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='00cd01d098d1$94047010$bc0d5030$@storageio.com' \
--to=greg@storageio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.