Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp that should
not generate any more change events for you. Please post
for comparison that this new version returns the same data
as the old one.
move the old mpath_prio_netapp to /sbin/mpath_prio_netapp.old
cp the new one into sbin.
post the results of the following script
(adjust device range accordingly)
for i in sd[a-z]; do /sbin/mpath_prio_netapp.old $i; done
for i in sd[a-z]; do /sbin/mpath_prio_netapp $i; done
Verify that the same values are returned from each run,
and update the bug with your results.
Once you verify that the updated prio checker no longer
generates change events, start up multipathd again and
verify that this continues to be true. Thanks!
Excellent, you're still interested. I've got a fix for you to try.
Attached is a custom version of mpath_prio_netapp that should
not generate any more change events for you. Please post
for comparison that this new version returns the same data
as the old one.
move the old mpath_prio_netapp to /sbin/mpath_ prio_netapp. old
cp the new one into sbin.
post the results of the following script
(adjust device range accordingly)
for i in sd[a-z]; do /sbin/mpath_ prio_netapp. old $i; done
for i in sd[a-z]; do /sbin/mpath_ prio_netapp $i; done
Verify that the same values are returned from each run,
and update the bug with your results.
Once you verify that the updated prio checker no longer
generates change events, start up multipathd again and
verify that this continues to be true. Thanks!