Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: paul.grabinar@ranbarg.com (Paul Grabinar)
Subject: nvme-cli format timeout
Date: Thu, 23 Jul 2015 21:22:30 +0100	[thread overview]
Message-ID: <55B14D06.6010502@ranbarg.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1507232009580.15930@localhost.lm.intel.com>

On 23/07/15 21:11, Keith Busch wrote:
> On Thu, 23 Jul 2015, Paul Grabinar wrote:
>> Hi,
>>
>> I am aware of some NVMe drives that take well over 60 seconds to perform
>> a format and therefore timeout during the format command issued by
>> nvme-cli.
>>
>> We might want to consider increasing the timeout. The following patch is
>> an example to show what I mean.
>
> Good idea. We should probably make this a parameter as well as up
> the timeout. Only the passthru command takes the timeout request as a
> parameter for some reason.
>
> If you want to post a pull request on github, we can apply it from there.
>

Thanks.
I'll post a pull request. As you say though, having a timeout parameter
would probably be even better.

      reply	other threads:[~2015-07-23 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 20:03 nvme-cli format timeout Paul Grabinar
2015-07-23 20:11 ` Keith Busch
2015-07-23 20:22   ` Paul Grabinar [this message]

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=55B14D06.6010502@ranbarg.com \
    --to=paul.grabinar@ranbarg.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