From: marc.smith@mcc.edu (Marc Smith)
Subject: Linux 4.9.8 + NVMe CiB Issue
Date: Fri, 31 Mar 2017 09:26:32 -0400 [thread overview]
Message-ID: <CAHkw+LdOnTdwpSR8=aefeLk51aUCg9NzsDSJdT1t-S97jP0tng@mail.gmail.com> (raw)
In-Reply-To: <20170310002745.GH14329@localhost.localdomain>
Just an update in case anyone else stumbles upon this thread with the
same issue: Intel reviewed the logs from the drives and determined the
NVMe drives are hitting their maximum operating temperature and then
shutting down.
--Marc
On Thu, Mar 9, 2017@7:27 PM, Keith Busch <keith.busch@intel.com> wrote:
> On Thu, Mar 09, 2017@03:25:01PM -0500, Marc Smith wrote:
>> Hi,
>>
>> We opened a support case with Intel (# 02641251) but we aren't making
>> much progress... they looked at log files from /var/log/ on our system
>> and now seem to be blaming warning/error log lines from
>> Corosync/Pacemaker on the issue. =)
>>
>> We're still able to reproduce this issue with high load... the NVMe
>> drives "drop out", randomly, not always the same drive, when pushing
>> I/O across all of our NVMe drives.
>>
>> We don't mind to keep pushing on the Intel NVMe hardware support
>> front, but looking for confirmation that its believed based on the
>> kernel log messages posted, that this is an issue with the NVMe drives
>> themselves (eg, firmware)?
>
> This genuinely looks like the drives have stopped responding and needs
> to be directed to the drive vendor.
next prev parent reply other threads:[~2017-03-31 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 19:27 Linux 4.9.8 + NVMe CiB Issue Marc Smith
2017-02-15 21:12 ` Keith Busch
2017-02-16 15:37 ` Marc Smith
2017-02-20 16:43 ` Marc Smith
2017-02-21 16:42 ` Marc Smith
2017-03-09 20:25 ` Marc Smith
2017-03-10 0:27 ` Keith Busch
2017-03-31 13:26 ` Marc Smith [this message]
2017-03-31 14:07 ` Keith Busch
2017-03-31 14:33 ` Marc Smith
2017-04-01 7:13 ` Dennis Mungai
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='CAHkw+LdOnTdwpSR8=aefeLk51aUCg9NzsDSJdT1t-S97jP0tng@mail.gmail.com' \
--to=marc.smith@mcc.edu \
/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.