Dne 29. 01. 22 v 0:21 Martin Wilck napsal(a):
On Fri, 2022-01-28 at 22:06 +0100, Zdenek Kabelac wrote:
Dne 28. 01. 22 v 19:46 Martin Wilck napsal(a):
On Fri, 2022-01-28 at 18:47 +0100, Zdenek Kabelac wrote:
Dne 28. 01. 22 v 17:02 Martin Wilck napsal(a):
On Fri, 2022-01-28 at 16:57 +0100, Martin Wilck wrote:
Well it is at the point we need to know exactly which device in which
state
causes you problem. Then we need to see what is wrong in the whole
process.
This is how multipathd loads the multipath map before the error occurs:
[ 127.352614] localhost multipathd[1059]: 3600a098000aad1e300000b4b5a275d45: reload [0 134217728 multipath 3 pg_init_retries 50 queue_if_no_path 1 alua 2 1 service-time 0 1 1 8:80 1 service-time 0 2 1 8:16 1 8:144 1]
All I'm saying here is - that the proposed patch is not fixing bug -
but
rather masking/minimizing window for error.
AFAICS my patch eliminates the window for this error entirely.
Ok now I see that there is already skip for DM_SUSPENDED
and you patch likely only tries to preserve some existing state of links.
I'll need to get in touch with Peter here.
I guess the idea behind was to avoid read of device that will be resumed and
will automatically get a new event - and suspened device itself cannot change
- but that fact it's been loosing existing state was missed - I'm wondering
why this was not seen as problem before.
Regars
Zdene
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/dm-devel
