From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michal Soltys <msoltyspl@yandex.pl>
Subject: Re: Assemblin journaled array fails
Date: Mon, 6 Jul 2020 10:07:17 +0200
Message-ID: <4577498e-4124-ac6f-9d76-1f039fa1ba80@yandex.pl>
References: <f8c61278-1758-66cd-cf25-8a118cb12f58@yandex.pl>
 <0cf6454d-a8b5-4bee-5389-94b23c077050@yandex.pl>
 <CAPhsuW51u6KWLvUntMXPU7stu7oSA+d-yT6zf7G0zCETzLWwiA@mail.gmail.com>
 <49efa0d2-b44c-ec85-5e44-fb93a15001e7@yandex.pl>
 <4df42e3d-ad2b-dfc2-3961-49ada4ea7eaf@yandex.pl>
 <CAPhsuW5kk0G9PSfEADc8+rn=QT2z4ogjuV98qWsH_s_WBic-5w@mail.gmail.com>
 <71f58507-314e-4a1d-dd50-41a60d76521b@yandex.pl>
 <CAPhsuW59Q7mU9WH36RHs9kb-TMk7FmrQL+JCApupf_TZtpWynA@mail.gmail.com>
 <4a03e900-61a8-f150-9be8-739e88ba8ce6@yandex.pl>
 <CAPhsuW4BZE-DeESsq-coNx5_KZrfHjP=d9YOjOPqPji5kQBXjg@mail.gmail.com>
 <a772ede5-1d6f-e7cd-e949-a5d81d0fdbd1@yandex.pl>
 <CAPhsuW5hwAMTy8ozpsT+n5F3M7NzKqBdheFZvnouZEv8hEqAxQ@mail.gmail.com>
 <4b426e56-f971-67cf-81c0-63e035bf492a@yandex.pl>
 <CAPhsuW6fvgRCz7X7nnCEof4+yy2fTsxShNCuqTkMC0JQpj6gKw@mail.gmail.com>
 <57247f5e-ec38-fb8c-9684-abbe699945fb@yandex.pl>
 <CAPhsuW4hnpsbhQWWNKqgnw4nhp4Ho+gFbPU2fGjoMOcM8y7L+Q@mail.gmail.com>
 <15a3dd66-39a9-894d-3e72-d231cf36758e@yandex.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Return-path: <linux-raid-owner@vger.kernel.org>
In-Reply-To: <15a3dd66-39a9-894d-3e72-d231cf36758e@yandex.pl>
Content-Language: en-US
Sender: linux-raid-owner@vger.kernel.org
To: Song Liu <song@kernel.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
List-Id: linux-raid.ids

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@yandex.pl> 
>> 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 ?