All of lore.kernel.org
 help / color / mirror / Atom feed
From: swise@opengridcomputing.com (Steve Wise)
Subject: Windows NVMeoF client - debug assistance requested
Date: Tue, 21 Jun 2016 09:22:52 -0500	[thread overview]
Message-ID: <007201d1cbc8$65846c10$308d4430$@opengridcomputing.com> (raw)
In-Reply-To: <ad34b8cf5ca544588b2d3fc9cc63fba0@bowex36e.micron.com>


> 
> Similar problems?  What kind of problems.
>

The same, I think.  From me in an earlier private email:

> > When using nvmf-all.2 branch from infradead, I can discover/connect ok to
> > a target, but when I do an mkfs.ext4 on the nvmf device, it succeeds, but
> > the data isn't written to the device.  So a subsequent mount will fail.  I
> > backed up to nvmf-all branch, and it works fine.

Christoph provided me a patch to include, and I think it is here in nvmf-all.3:

commit bb18f6e76300970383d66dbc17936b854f6d79e6
Author: Christoph Hellwig <hch at lst.de>
Date:   Tue Jun 14 09:27:53 2016 +0200

    nvmet: more fixups for the op vs flags split

    Signed-off-by: Christoph Hellwig <hch at lst.de>

I didn't try .2 + just this fix, because .3 popped out and went to that version.



Steve.

  reply	other threads:[~2016-06-21 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21  1:50 Windows NVMeoF client - debug assistance requested Robert Randall (rrandall)
2016-06-21 13:56 ` Steve Wise
2016-06-21 14:16   ` Robert Randall (rrandall)
2016-06-21 14:22     ` Steve Wise [this message]
2016-06-21 14:19 ` Sagi Grimberg
2016-06-21 14:55   ` Robert Randall
2016-06-21 15:20     ` Robert Randall
2016-06-21 16:02       ` Christoph Hellwig
2016-06-21 16:02       ` Robert Randall

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='007201d1cbc8$65846c10$308d4430$@opengridcomputing.com' \
    --to=swise@opengridcomputing.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.