About five years ago, we faced a somewhat simular issue with Symmetrix arrays, where the replicated LU of a SRDF pair (R2) was flagged read-only by the kernel upon discovery. Splitting the pair with a symcli command made the LU read-write from the array controller point of view, but the Linux kernel would not promote it read-write dynamically.
I don't know if the Symmetrix array also use a unit attention to signal the change to the initiators. If it does, it might be worth trying to address both the 3par peer persistance and the Symmetrix SRDF situations.
On the other hand, if the SRDF R2 rw promotion issue has been fixed since, the patch might give guidance about where/how to plug the 3par peer persistance ghost path rescans.
Best regards,
Christophe Varoqui
OpenSVC
On Tue, Apr 14, 2015 at 11:49 AM, Bart Van Assche <bart.vanassche@xxxxxxxxxxx> wrote:
On 04/14/15 10:14, Hannes Reinecke wrote:
What we can try is to listen to uevents for the device capacity
change or ALUA state changes, and retry the read capacity for those
events.
Any mechanism that relies on uevents would be asynchronous. We need a way to ensure that the capacity data is up to date before any application starts using that data. In this context that means before multipath starts queueing I/O to a path. This might be challenging when processing uevents asynchronously ...
Bart.
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
