Re: [dm-devel] new multipath device mistakenly replaced another PV in existing volume group

2017-04-25 Thread Neutron Sharc
Benjamin: thanks for replying. We have found the root cause to be stale read buffer at backend. After zeroing out read buffer upon read miss the problem is gone. -Shawn On Tue, Apr 25, 2017 at 9:39 AM, Benjamin Marzinski wrote: > On Wed, Apr 19, 2017 at 02:58:47PM -0700, Neutron Sharc wr

[dm-devel] new multipath device mistakenly replaced another PV in existing volume group

2017-04-19 Thread Neutron Sharc
I'm seeing a strange problem (iscsi LUNs + dm-multipath + lvm) that I will walk through an example to explain. I have an iscsi target machine that exposes many iscsi LUNs. Iscsi initiator logs in 4 iscsi LUNs (vol1_[0-3]), creates a multipath device for each LUN (/dev/mapper/vol1_[0-3]), and comb