On Mon, Jul 6, 2020 at 1:07 AM Michal Soltys <msoltyspl@xxxxxxxxx> wrote:
>
> On 20/06/25 18:11, Michal Soltys wrote:
> > On 6/24/20 1:13 AM, Song Liu wrote:
> >> On Tue, Jun 23, 2020 at 6:17 AM Michal Soltys <msoltyspl@xxxxxxxxx>
> >> wrote:
> >>
> >> Hmm.. this is weird, as I think I marked every instance of set_bit
> >> MD_SB_CHANGE_PENDING.
> >> Would you mind confirm those are to the other array with something like:
> >>
> >> diff --git i/drivers/md/md.c w/drivers/md/md.c
> >> index dbbc8a50e2ed2..e91acfdcec032 100644
> >> --- i/drivers/md/md.c
> >> +++ w/drivers/md/md.c
> >> @@ -8480,7 +8480,7 @@ bool md_write_start(struct mddev *mddev, struct
> >> bio *bi)
> >> mddev->in_sync = 0;
> >> set_bit(MD_SB_CHANGE_CLEAN, &mddev->sb_flags);
> >> set_bit(MD_SB_CHANGE_PENDING, &mddev->sb_flags);
> >> - pr_info("%s set MD_SB_CHANGE_PENDING\n",
> >> __func__);
> >> + pr_info("%s: md: %s set
> >> MD_SB_CHANGE_PENDING\n", __func__, mdname(mddev));
> >> md_wakeup_thread(mddev->thread);
> >> did_change = 1;
> >> }
> >>
> >> Thanks,
> >> Song
> >>
> >
> > dmesg attached
> > - md127 - journal
> > - md126 - the other raid
> > - md125 - the problematic one
>
> So, what kind of next step after this ?
Sorry for the delay. I read the log again, and found the following
line caused this issue:
[ +16.088243] r5l_write_super_and_discard_space set MD_SB_CHANGE_PENDING
The attached patch should workaround this issue. Could you please give it a try?
Thanks,
song
Attachment:
0001-md-raid5-cache-clear-MD_SB_CHANGE_PENDING-before-flu.patch
Description: Binary data
