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=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,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 C2C7AC433ED for ; Wed, 28 Apr 2021 14:03:34 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 1D4A161442 for ; Wed, 28 Apr 2021 14:03:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1D4A161442 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mit.edu Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 694F16B0036; Wed, 28 Apr 2021 10:03:33 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 6453B6B006E; Wed, 28 Apr 2021 10:03:33 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4E69F6B0070; Wed, 28 Apr 2021 10:03:33 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0006.hostedemail.com [216.40.44.6]) by kanga.kvack.org (Postfix) with ESMTP id 295F06B0036 for ; Wed, 28 Apr 2021 10:03:33 -0400 (EDT) Received: from smtpin03.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id CA6C14435 for ; Wed, 28 Apr 2021 14:03:32 +0000 (UTC) X-FDA: 78081943464.03.817AC50 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by imf09.hostedemail.com (Postfix) with ESMTP id 4E3AF6001F98 for ; Wed, 28 Apr 2021 14:03:22 +0000 (UTC) Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13SE3HW3018990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 28 Apr 2021 10:03:17 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id DB1D515C3C3D; Wed, 28 Apr 2021 10:03:16 -0400 (EDT) Date: Wed, 28 Apr 2021 10:03:16 -0400 From: "Theodore Ts'o" To: kernel test robot Cc: Harshad Shirwadkar , LKML , Linux Memory Management List , lkp@lists.01.org, lkp@intel.com, dm-devel@redhat.com Subject: Re: [ext4] 21175ca434: mdadm-selftests.enchmarks/mdadm-selftests/tests/01r1fail.fail Message-ID: References: <20210427081539.GF32408@xsang-OptiPlex-9020> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210427081539.GF32408@xsang-OptiPlex-9020> X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 4E3AF6001F98 X-Stat-Signature: 6zu3ecpnmejjznqu48gdfruxxeh8ors6 Received-SPF: none (mit.edu>: No applicable sender policy available) receiver=imf09; identity=mailfrom; envelope-from=""; helo=outgoing.mit.edu; client-ip=18.9.28.11 X-HE-DKIM-Result: none/none X-HE-Tag: 1619618602-442459 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: (Hmm, why did you cc linux-km on this report? I would have thought dm-devel would have made more sense?) On Tue, Apr 27, 2021 at 04:15:39PM +0800, kernel test robot wrote: > > FYI, we noticed the following commit (built with gcc-9): > > commit: 21175ca434c5d49509b73cf473618b01b0b85437 ("ext4: make prefetch_block_bitmaps default") > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master > > in testcase: mdadm-selftests > version: mdadm-selftests-x86_64-5d518de-1_20201008 > with following parameters: > > disk: 1HDD > test_prefix: 01r1 > ucode: 0x21 So this failure makes no sense to me. Looking at the kmesg failure logs, it's failing in the md layer: kern :info : [ 99.775514] md/raid1:md0: not clean -- starting background reconstruction kern :info : [ 99.783372] md/raid1:md0: active with 3 out of 4 mirrors kern :info : [ 99.789735] md0: detected capacity change from 0 to 37888 kern :info : [ 99.796216] md: resync of RAID array md0 kern :crit : [ 99.900450] md/raid1:md0: Disk failure on loop2, disabling device. md/raid1:md0: Operation continuing on 2 devices. kern :crit : [ 99.918281] md/raid1:md0: Disk failure on loop1, disabling device. md/raid1:md0: Operation continuing on 1 devices. kern :info : [ 100.835833] md: md0: resync interrupted. kern :info : [ 101.852898] md: resync of RAID array md0 kern :info : [ 101.858347] md: md0: resync done. user :notice: [ 102.109684] /lkp/benchmarks/mdadm-selftests/tests/01r1fail... FAILED - see /var/tmp/01r1fail.log and /var/tmp/fail01r1fail.log for details The referenced commit just turns block bitmap prefetching in ext4. This should not cause md to failure; if so, that's an md bug, not an ext4 bug. There should not be anything that the file system is doing that would cause the kernel to think there is a disk failure. By the way, the reproduction instructions aren't working currently: > To reproduce: > > git clone https://github.com/intel/lkp-tests.git > cd lkp-tests > bin/lkp install job.yaml # job file is attached in this email This fails because lkp is trying to apply a patch which does not apply with the current version of the md tools. > bin/lkp split-job --compatible job.yaml > bin/lkp run compatible-job.yaml And the current versions lkp don't generate a compatible-job.yaml file when you run "lkp split-job --compatable"; instead it generates a new yaml file with a set of random characters to generate a unique name. (What Multics parlance would be called a "shriek name"[1] :-) Since I was having trouble running the reproduction; could you send the /var/tmp/*fail.logs so we could have a bit more insight what is going on? Thanks! - Ted