From: lixiaokeng <lixiaokeng@huawei.com>
To: Martin Wilck <mwilck@suse.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
dm-devel mailing list <dm-devel@redhat.com>
Cc: linfeilong <linfeilong@huawei.com>,
"liuzhiqiang \(I\)" <liuzhiqiang26@huawei.com>,
lihaotian9@huawei.com
Subject: Re: [dm-devel] [QUESTION]: multipath device with wrong path lead to metadata err
Date: Tue, 19 Jan 2021 20:46:19 +0800 [thread overview]
Message-ID: <c0b51442-4be4-c2d8-01a1-90240194c48c@huawei.com> (raw)
In-Reply-To: <af0f31ce3d83f15049598de0c96c4fde6eb553f6.camel@suse.com>
Hi Martin,
I have tested 0.7.7 and 0.8.5 code.They both have metadate error.
I find I missed some information in last email. Ip1 log in between (1)
and (2) and sdi became a path of 36001405b7679bd96b094bccbf971bc90, but
uevents weren't deal until （3） finished.
The details described are base on code 0.7.7. I think similar process
exists in 0.8.5 but there may be another to cause error.
The latest "queue" code isn't tested. I will try.
Regards,
Lixiaokeng
On 2021/1/19 17:41, Martin Wilck wrote:
> Hi Lixiaokeng,
>
> On Mon, 2021-01-18 at 19:08 +0800, lixiaokeng wrote:
>> Hi
>> When we make IO stress test on multipath device, there will
>> be a metadata err because of wrong path.
>>
>
> thanks for the detailed report and analysis, also for sharing
> your test scripts! I'll take a closer look asap. Meanwhile, please
> confirm which multipath-tools version you were using, and whether this
> occurs with the latest "queue" code:
>
> https://github.com/openSUSE/multipath-tools/tree/queue
>
> Regards
> Martin
>
>
> .
>
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-01-19 12:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 11:08 [dm-devel] [QUESTION]: multipath device with wrong path lead to metadata err lixiaokeng
2021-01-19 9:41 ` Martin Wilck
2021-01-19 12:46 ` lixiaokeng [this message]
2021-01-19 21:57 ` Martin Wilck
2021-01-20 2:30 ` lixiaokeng
2021-01-20 14:07 ` Martin Wilck
2021-01-25 1:33 ` lixiaokeng
2021-01-25 12:28 ` Martin Wilck
2021-01-26 6:40 ` lixiaokeng
2021-01-26 11:14 ` lixiaokeng
2021-01-26 23:11 ` Martin Wilck
2021-01-28 8:27 ` lixiaokeng
2021-01-28 21:15 ` Martin Wilck
2021-02-04 11:25 ` lixiaokeng
2021-02-04 14:56 ` Martin Wilck
2021-02-05 11:49 ` lixiaokeng
2021-01-20 13:02 ` Roger Heflin
2021-01-20 20:45 ` Martin Wilck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0b51442-4be4-c2d8-01a1-90240194c48c@huawei.com \
--to=lixiaokeng@huawei.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=lihaotian9@huawei.com \
--cc=linfeilong@huawei.com \
--cc=liuzhiqiang26@huawei.com \
--cc=mwilck@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.