On 07/23/2018 06:33 PM, Mike Snitzer wrote:
Hi,
I've opened the following public BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1607527
Feel free to add comments to that BZ if you have a redhat bugzilla
account.
But otherwise, happy to get as much feedback and discussion going purely
on the relevant lists. I've taken ~1.5 weeks to categorize and isolate
this issue. But I've reached a point where I'm getting diminishing
returns and could _really_ use the collective eyeballs and expertise of
the community. This is by far one of the most nasty cases of corruption
I've seen in a while. Not sure where the ultimate cause of corruption
lies (that the money question) but it _feels_ rooted in NVMe and is
unique to this particular workload I've stumbled onto via customer
escalation and then trying to replicate an rbd device using a more
approachable one (request-based DM multipath in this case).
I might be stating the obvious, but so far we only have considered
request-based multipath as being active for the _entire_ device.
To my knowledge we've never tested that when running on a partition.
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?
Cheers,
Hannes
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
