Re: [dm-devel] [PATCH 09/10] add disable_changed_wwids option

2017-02-28 Thread Zhangguanghui
evel@redhat.com> Subject: Re: [dm-devel] [PATCH 09/10] add disable_changed_wwids option On Sun, Oct 30, 2016 at 02:54:14PM +0100, Hannes Reinecke wrote: > On 10/29/2016 04:55 AM, Benjamin Marzinski wrote: > >If a LUN on a storage device gets remapped while in-use by multipath, > >

Re: [dm-devel] [PATCH 09/10] add disable_changed_wwids option

2016-11-05 Thread Xose Vazquez Perez
On 10/29/2016 04:55 AM, Benjamin Marzinski wrote: > If a LUN on a storage device gets remapped while in-use by multipath, > it's possible that the multipath device will continue writing to this > new LUN, causing corruption. This is not multipath's fault (users > should go remapping in-use

Re: [dm-devel] [PATCH 09/10] add disable_changed_wwids option

2016-10-30 Thread Hannes Reinecke
On 10/29/2016 04:55 AM, Benjamin Marzinski wrote: If a LUN on a storage device gets remapped while in-use by multipath, it's possible that the multipath device will continue writing to this new LUN, causing corruption. This is not multipath's fault (users should go remapping in-use LUNs), but

[dm-devel] [PATCH 09/10] add disable_changed_wwids option

2016-10-28 Thread Benjamin Marzinski
If a LUN on a storage device gets remapped while in-use by multipath, it's possible that the multipath device will continue writing to this new LUN, causing corruption. This is not multipath's fault (users should go remapping in-use LUNs), but it's possible for multipath to detect this and