From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7C409C43381 for ; Tue, 19 Feb 2019 12:17:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5648E21738 for ; Tue, 19 Feb 2019 12:17:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726817AbfBSMRM (ORCPT ); Tue, 19 Feb 2019 07:17:12 -0500 Received: from mx2.cyber.ee ([193.40.6.72]:37992 "EHLO mx2.cyber.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725805AbfBSMRM (ORCPT ); Tue, 19 Feb 2019 07:17:12 -0500 Subject: Re: ext4 corruption on alpha with 4.20.0-09062-gd8372ba8ce28 To: Jan Kara Cc: "Theodore Y. Ts'o" , linux-alpha@vger.kernel.org, LKML , linux-block@vger.kernel.org References: <1c26eab4-3277-9066-5dce-6734ca9abb96@linux.ee> <076b8b72-fab0-ea98-f32f-f48949585f9d@linux.ee> <20190216174536.GC23000@mit.edu> <20190218120209.GC20919@quack2.suse.cz> From: Meelis Roos Message-ID: <4e015688-8633-d1a0-308b-ba2a78600544@linux.ee> Date: Tue, 19 Feb 2019 14:17:09 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <20190218120209.GC20919@quack2.suse.cz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: et-EE Content-Transfer-Encoding: 7bit Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org >>>> The result of the bisection is >>>> [88dbcbb3a4847f5e6dfeae952d3105497700c128] blkdev: avoid migration stalls for blkdev pages >>>> >>>> Is that result relevant for the problem or should I continue bisecting between 4.20.0 and the so far first bad commit? >>> >>> Can you try reverting the commit and see if it makes the problem go away? >> >> Tried reverting it on top of 5.0.0-rc6-00153-g5ded5871030e and it seems >> to make the kernel work - emerge --sync succeeded. There is more to it. After running 5.0.0-rc6-00153-g5ded5871030e-dirty (with the revert of that patch) successfully for Gentoo update, I upgraded the kernel to 5.0.0-rc7-00011-gb5372fe5dc84-dirty (todays git + revert of this patch) and it broke on rsync again: RepoStorageException: command exited with status -6: rsync -a --link-dest /usr/portage --exclude=/distfiles --exclude=/local --exclude=/lost+found --exclude=/packages --exclude /.tmp-unverified-download-quarantine /usr/portage/ /usr/portage/.tmp-unverified-download-quarantine/ Nothing in dmesg. This means the real root reason is somewhere deeper and reverting this commit just made it less likely to happen. -- Meelis Roos