linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Bart.VanAssche@wdc.com (Bart Van Assche)
Subject: data corruption with 'splt' workload to XFS on DM cache with its 3 underlying devices being on same NVMe device
Date: Tue, 24 Jul 2018 14:25:41 +0000	[thread overview]
Message-ID: <bc63227473a19cb23d6b2bb38eefa564dfec1ffc.camel@wdc.com> (raw)
In-Reply-To: <e761830f-e3f7-3e88-1697-b4b150e84e5f@suse.de>

On Tue, 2018-07-24@08:00 +0200, Hannes Reinecke wrote:
> So, have you tested that request-based multipathing works on a partition 
> _at all_? I'm not sure if partition mapping is done correctly here; we 
> never remap the start of the request (nor bio, come to speak of it), so 
> it looks as if we would be doing the wrong things here.
> 
> Have you checked that partition remapping is done correctly?

I think generic_make_request() takes care of partition remapping by calling
blk_partition_remap(). generic_make_request() is called by submit_bio(). Is
that sufficient to cover all dm drivers?

Bart.

  parent reply	other threads:[~2018-07-24 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 16:33 data corruption with 'splt' workload to XFS on DM cache with its 3 underlying devices being on same NVMe device Mike Snitzer
2018-07-24  6:00 ` Hannes Reinecke
2018-07-24 13:07   ` Mike Snitzer
2018-07-24 13:22     ` Laurence Oberman
2018-07-24 13:51     ` Hannes Reinecke
2018-07-24 13:57       ` Laurence Oberman
2018-07-24 15:18         ` Mike Snitzer
2018-07-24 15:31           ` Laurence Oberman
2018-07-24 17:42     ` Christoph Hellwig
2018-07-24 14:25   ` Bart Van Assche [this message]
2018-07-24 15:07     ` Mike Snitzer

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=bc63227473a19cb23d6b2bb38eefa564dfec1ffc.camel@wdc.com \
    --to=bart.vanassche@wdc.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;
as well as URLs for NNTP newsgroup(s).