[dm-devel] [PATCH 2/2] multipathd: add recheck_wwid_time option to verify the path wwid

[Chongyun Wu]

On 2021/2/11 20:14, Martin Wilck wrote:

>>> But foremost, do we really have to try to deal with configuration
>>> mistakes as blatant as this? What if a user sets the same WWID for
>>> different devices, or re-uses the same WWID on different storage
>>> servers? I already hesitated about the code I added myself for
>>> catching
>>> user errors in the WWIDs file, but this seems even more far-
>>> fetched.
>>>
>>> Please convince me.
>>
>> Err.. An important customer corrupted their data and while they admit
>> that they were at fault, it's hard for them to guarantee that
>> something
>> like this won't happen in the future, and they asked if multipath
>> could
>> do a better job of catching these sorts of mistakes. Obviously this
>> is
>> more convincing when it's coming from your customer. But the fact
>> still
>> stands that this has happened to multiple users even with our
>> existing
>> code to catch this.
> 
> I wasn't aware of multiple affected users. I saw Chongyun's post and it
> looked to me as if this had happend once, likely in his organization.
> It wasn't even clear to me whether production data were affected.
> 
Had customers have made incorrect storage back-end operations during the 
expansion process, which has caused the destruction of customer data, which 
cannot be repaired using any tools. And I reproduce it in our lab too.
Customers definitely hope that multipath-tools can probide protection in
this case, becuase if it is important custmer data storage in the LUN, the
loss will be great.

-- 
Best Regard,
Chongyun Wu