From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Soltys Subject: Re: Assemblin journaled array fails Date: Mon, 22 Jun 2020 13:12:03 +0200 Message-ID: <4b426e56-f971-67cf-81c0-63e035bf492a@yandex.pl> References: <1767d7aa-6c60-7efb-bf37-6506f9aaa8a2@yandex.pl> <0cf6454d-a8b5-4bee-5389-94b23c077050@yandex.pl> <49efa0d2-b44c-ec85-5e44-fb93a15001e7@yandex.pl> <4df42e3d-ad2b-dfc2-3961-49ada4ea7eaf@yandex.pl> <71f58507-314e-4a1d-dd50-41a60d76521b@yandex.pl> <4a03e900-61a8-f150-9be8-739e88ba8ce6@yandex.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US-large Sender: linux-raid-owner@vger.kernel.org To: Song Liu Cc: linux-raid List-Id: linux-raid.ids On 6/20/20 2:14 AM, Song Liu wrote: > On Fri, Jun 19, 2020 at 4:35 AM Michal Soltys wrote: >> >> On 6/17/20 7:11 PM, Song Liu wrote: >>>> >>>>> 1. There are two pr_debug() calls in handle_stripe(): >>>>> pr_debug("handling stripe %llu, state=%#lx cnt=%d, " >>>>> pr_debug("locked=%d uptodate=%d to_read=%d" >>>>> >>>>> Did you enable all of them? Or only the first one? >>>> >>>> I enabled all of them (I think), to be precise: >>>> >>>> echo -n 'func handle_stripe +p' >/sys/kernel/debug/dynamic_debug/control >>>> >>>> Haven't seen any `locked` lines though. >>> >>> That's a little weird, and probably explains why we stuck. Could you >>> please try the attached patch? >>> >>> Thanks, >>> Song >>> >> >> I've started assembly with the above patch, the output can be inspected >> from this file: >> >> https://ufile.io/yx4bbcb4 >> >> This is ~5mb packed dmesg from start of the boot to the relevant parts, >> unpacks to ~150mb file. > > Thanks for the trace. Looks like we may have some issues with > MD_SB_CHANGE_PENDING. > Could you please try the attached patch? Should I run this along with pr_debugs from the previous patch enabled ?