Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2713282imj; Mon, 11 Feb 2019 07:22:52 -0800 (PST) X-Google-Smtp-Source: AHgI3IZqGHunPSU2yRStJHMjm18lnQwQyKuym+AsBlwlDgszEVzb56aQyL0dnwtDorPK7ia5P9Am X-Received: by 2002:a17:902:bd82:: with SMTP id q2mr11850336pls.156.1549898572737; Mon, 11 Feb 2019 07:22:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549898572; cv=none; d=google.com; s=arc-20160816; b=s6gJ3Se0Of3DvtZsGyutUfjCpVjFoVFpwjf+w6KG+bOUgIci/zkIrHV30dhQNrh4sH DtDqcueNWpySREXUoF4I0v9/lh1W4nHqdpNAsbCykog4fX4D9oZHZRR8+4ahcO2Z8M2u bQo3VfKRG9Hz9KHE8TfNpGZQ0bq6sbfm/Wj4n9vn/8fwSeEEAt/hiQwYFnQeKD2W0ODS eM/rvuveANMwOXWKfOG49sgEmUJVM6SO1OgTLwf/Zj+Dg8evWb2wc6Tqy3NwCMABXEVC mxAQ+9klQ17rnUHxYXZm7Sc6ZMbh11CRSXaqRbbMs7tLuJ8G6tETgcyiplO2jli14VJK 0inA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:message-id:date:subject:cc:to:from:dkim-signature; bh=rKA+/UvRXDP6sz6M9fyG+cbLCzZgCeRXhftfoPNLaCA=; b=dZWao75GbWT/16PNQfeb/kyiqHf+dOIGcGycMgZGGm55wKGjrDDuzrfNuakiUcDqBR uv1IRJ1GSBq/h+etfHKhlPxbosJCvZV1uoEmRHvGWDqqTkp7RXwCQA1J7LWBmYq8JlR2 6eap/yQejmoYclvo2rixsWvuZdqlVgK+gG8VWlRuNkq+hTjeTKNU/mj0r9pTbUIQXGFk kMyQg6Sk40ejDWpPRuccEquvvqV9FYWMY9Sv7u61Cx2tyzHLQ3EVjmUBbKKsl6tiEe0z rQGmaQ3fTyHQqPAzhBGCufMLONZfHSF9eGONgyTy0IoEtnZ5JpOtpEKkuhbTEbOPQx2Q yn+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@stwm.de header.s=stwm-20170627 header.b=M22rJE+g; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l94si11018954plb.209.2019.02.11.07.22.24; Mon, 11 Feb 2019 07:22:52 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@stwm.de header.s=stwm-20170627 header.b=M22rJE+g; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391323AbfBKPVc (ORCPT + 99 others); Mon, 11 Feb 2019 10:21:32 -0500 Received: from mailin.studentenwerk.mhn.de ([141.84.225.229]:57622 "EHLO email.studentenwerk.mhn.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731645AbfBKPVb (ORCPT ); Mon, 11 Feb 2019 10:21:31 -0500 X-Greylist: delayed 511 seconds by postgrey-1.27 at vger.kernel.org; Mon, 11 Feb 2019 10:21:29 EST Received: from mailhub.studentenwerk.mhn.de (mailhub.studentenwerk.mhn.de [127.0.0.1]) by email.studentenwerk.mhn.de (Postfix) with ESMTP id 43yq6K0NxhzRhS8; Mon, 11 Feb 2019 16:12:57 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stwm.de; s=stwm-20170627; t=1549897977; bh=rKA+/UvRXDP6sz6M9fyG+cbLCzZgCeRXhftfoPNLaCA=; h=From:To:Cc:Subject:Date:From; b=M22rJE+glZIlij0kG+tSwGfqE/3zKPHHiobPhIMKiSkBH/6Wmar1NLeaNDBrZ2Afv d2ByGng9zdVlxZg84yxXvC0hZFsgkXU65QUVSEM5fyi2D1bSN7u3Vk927ff0x3o4cH NRC9Vs0KvD35dpeCaB3pC60EDM2UfDN+9+cLW54/i9CTcga7FoMGc4E69eeLHFm5bR Eud7vNziyXzbPv5mmEvZ2jiSRABwI0tNSAJsyxu4cwnp7PSmEOVpge2t+fSa60mdAr kjTdUkKPMCQ8YBv9pqni1MYTpEjNGWCEeXDpoJnc8AVVxi6HCwCbRbdGNel97uanQX 3P+NicGXn1jng== From: Wolfgang Walter To: Jens Axboe Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, Guoqing Jiang Subject: linux 4.19.19: md0_raid:1317 blocked for more than 120 seconds. Date: Mon, 11 Feb 2019 16:12:56 +0100 Message-ID: <2131016.q2kFhguZXe@stwm.de> User-Agent: KMail/4.14.3 (Linux/4.18.12-041812-generic; KDE/4.14.13; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org With 4.19.19 we see sometimes the following issue (practically only wit= h blk_mq, though): Feb 4 20:04:46 tettnang kernel: [252300.060165] INFO: task md0_raid1:3= 17 blocked for more than 120 seconds. Feb 4 20:04:46 tettnang kernel: [252300.060188] Not tainted 4.19= .19-debian64.all+1.1 #1 Feb 4 20:04:46 tettnang kernel: [252300.060197] "echo 0 > /proc/sys/ke= rnel/hung_task_timeout_secs" disables this message. Feb 4 20:04:46 tettnang kernel: [252300.060207] md0_raid1 D 0= 317 2 0x80000000 Feb 4 20:04:46 tettnang kernel: [252300.060211] Call Trace: Feb 4 20:04:46 tettnang kernel: [252300.060222] ? __schedule+0x2a2/0x= 8c0 Feb 4 20:04:46 tettnang kernel: [252300.060226] ? _raw_spin_unlock_ir= qrestore+0x20/0x40 Feb 4 20:04:46 tettnang kernel: [252300.060229] schedule+0x32/0x90 Feb 4 20:04:46 tettnang kernel: [252300.060241] md_super_wait+0x69/0x= a0 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060247] ? finish_wait+0x80/0x= 80 Feb 4 20:04:46 tettnang kernel: [252300.060255] md_bitmap_wait_writes= +0x8e/0xa0 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060263] ? md_bitmap_get_count= er+0x42/0xd0 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060271] md_bitmap_daemon_work= +0x1e8/0x380 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060278] ? md_rdev_init+0xb0/0= xb0 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060285] md_check_recovery+0x2= 6/0x540 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060290] raid1d+0x5c/0xf00 [ra= id1] Feb 4 20:04:46 tettnang kernel: [252300.060294] ? preempt_count_add+0= x79/0xb0 Feb 4 20:04:46 tettnang kernel: [252300.060298] ? lock_timer_base+0x6= 7/0x80 Feb 4 20:04:46 tettnang kernel: [252300.060302] ? _raw_spin_unlock_ir= qrestore+0x20/0x40 Feb 4 20:04:46 tettnang kernel: [252300.060304] ? try_to_del_timer_sy= nc+0x4d/0x80 Feb 4 20:04:46 tettnang kernel: [252300.060306] ? del_timer_sync+0x35= /0x40 Feb 4 20:04:46 tettnang kernel: [252300.060309] ? schedule_timeout+0x= 17a/0x3b0 Feb 4 20:04:46 tettnang kernel: [252300.060312] ? preempt_count_add+0= x79/0xb0 Feb 4 20:04:46 tettnang kernel: [252300.060315] ? _raw_spin_lock_irqs= ave+0x25/0x50 Feb 4 20:04:46 tettnang kernel: [252300.060321] ? md_rdev_init+0xb0/0= xb0 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060327] ? md_thread+0xf9/0x16= 0 [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060330] ? r1bio_pool_alloc+0x= 20/0x20 [raid1] Feb 4 20:04:46 tettnang kernel: [252300.060336] md_thread+0xf9/0x160 = [md_mod] Feb 4 20:04:46 tettnang kernel: [252300.060340] ? finish_wait+0x80/0x= 80 Feb 4 20:04:46 tettnang kernel: [252300.060344] kthread+0x112/0x130 Feb 4 20:04:46 tettnang kernel: [252300.060346] ? kthread_create_work= er_on_cpu+0x70/0x70 Feb 4 20:04:46 tettnang kernel: [252300.060350] ret_from_fork+0x35/0x= 40 I saw that there was a similar problem with raid10 and an upstream patc= h e820d55cb99dd93ac2dc949cf486bb187e5cd70d md: fix raid10 hang issue caused by barrier by Guoqing Jiang I wonder if there is a similar fix needed for raid1? Regards, --=20 Wolfgang Walter Studentenwerk M=FCnchen Anstalt des =F6ffentlichen Rechts