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=-4.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, PDS_BAD_THREAD_QP_64,SPF_HELO_NONE,SPF_PASS autolearn=no 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 1A899C2B9F4 for ; Thu, 17 Jun 2021 10:17:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F1B46611CE for ; Thu, 17 Jun 2021 10:17:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231833AbhFQKT6 (ORCPT ); Thu, 17 Jun 2021 06:19:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230269AbhFQKTu (ORCPT ); Thu, 17 Jun 2021 06:19:50 -0400 Received: from outbound5.mail.transip.nl (outbound5.mail.transip.nl [IPv6:2a01:7c8:7c9:ca11:136:144:136:9]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AB0BEC061574 for ; Thu, 17 Jun 2021 03:17:39 -0700 (PDT) Received: from submission4.mail.transip.nl (unknown [10.103.8.155]) by outbound5.mail.transip.nl (Postfix) with ESMTP id 4G5J011Y8KzHCfF; Thu, 17 Jun 2021 12:17:37 +0200 (CEST) Received: from exchange.transipgroup.nl (unknown [81.4.116.210]) by submission4.mail.transip.nl (Postfix) with ESMTPSA id 4G5J003GGnznTdR; Thu, 17 Jun 2021 12:17:36 +0200 (CEST) Received: from VM16171.groupdir.nl (10.131.120.71) by VM16171.groupdir.nl (10.131.120.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.15; Thu, 17 Jun 2021 12:17:35 +0200 Received: from VM16171.groupdir.nl ([81.4.116.210]) by VM16171.groupdir.nl ([81.4.116.210]) with mapi id 15.02.0792.015; Thu, 17 Jun 2021 12:17:35 +0200 From: Robin Geuze To: Ilya Dryomov CC: Ceph Development Subject: Re: All RBD IO stuck after flapping OSD's Thread-Topic: All RBD IO stuck after flapping OSD's Thread-Index: AQHXMQs7yqmta0olA0ygBmx0d4s7EKq0G68AgAFka/SABi6BAIBbPDuXgAE5TYCAACJLAv//77AAgAArXHM= Date: Thu, 17 Jun 2021 10:17:35 +0000 Message-ID: References: <47f0a04ce6664116a11cfdb5a458e252@nl.team.blue> <8eb12c996e404870803e9a7c77e508d6@nl.team.blue> <666938090a8746a7ad8ae40ebf116e1c@nl.team.blue> <21c4b9e08c4d48d6b477fc61d1fccba3@nl.team.blue>, In-Reply-To: Accept-Language: en-GB, nl-NL, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.4.116.242] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: ClueGetter at submission4.mail.transip.nl DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=transip-a; d=nl.team.blue; t=1623925056; h=from:subject:to:cc: references:in-reply-to:date:mime-version:content-type; bh=04QG5ptqNcvcLU9w5l5uB6mostFjxW53VH4onu1uZqA=; b=FVn2NxsHmAz1b91wIes2M6jTN+6yW1g7eGK5ISPCpa5vQRxY+mEHXK6hPKd5EyC0O2nH3L gG8k+uwL9GG5d62EY36igOXmfy2b/7emAgDuG+7i3fV+TIA5ow2pyfpyUTN3oYBlg/Qhyv 9fMMfLt0LefWCPaLqt8r2YLwHCNE4hwEzCYvXPYHq++MIMOG2pcUfW06/B+pS4rJ30Lxsn p6YqsgzUYJdG2nD91rsU0ug+BijBGgdRkGw19B91IKutRHGfDxD9F5kXVukac+8gKVi4k/ Nk+fmQU+3Slj+Bh4b/BMP5NIwgdnzYvZwVhaJ3VTqAGLkY1YX4jj4uKX62wpYg== X-Report-Abuse-To: abuse@transip.nl Precedence: bulk List-ID: X-Mailing-List: ceph-devel@vger.kernel.org Hey Ilya, We've added some extra debug info to the fileshare from before, including t= he sysrq-trigger output. Regards, Robin Geuze =20 From: Ilya Dryomov Sent: 17 June 2021 11:40:54 To: Robin Geuze Cc: Ceph Development Subject: Re: All RBD IO stuck after flapping OSD's =A0 =20 On Thu, Jun 17, 2021 at 10:42 AM Robin Geuze wro= te: > > Hey Ilya, > > We triggered the issue at roughly 13:05, so the problem cannot have occur= red before 13:00. > > We've also (in the wild, haven't reproduced that exact case yet) seen thi= s occur without any stacktraces or stuck threads. The only "common" factor = is that we see the watch errors, always at least twice within 1 or 2 minute= s if its broken. Ah, I guess I got confused by timestamps in stuck_kthreads.md. I grepped for "pre object map update" errors that you reported initially and didn't see any. With any sort of networking issues, watch errors are expected. I'll take a deeper look at syslog_stuck_krbd_shrinked. Thanks, =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ilya > > Regards, > > Robin Geuze > > From: Ilya Dryomov > Sent: 17 June 2021 10:36:33 > To: Robin Geuze > Cc: Ceph Development > Subject: Re: All RBD IO stuck after flapping OSD's > > On Wed, Jun 16, 2021 at 1:56 PM Robin Geuze wr= ote: > > > > Hey Ilya, > > > > Sorry for the long delay, but we've finally managed to somewhat reliabl= y reproduce this issue and produced a bunch of debug data. Its really big, = so you can find the files here: https://dionbosschieter.stackstorage.com/s/= RhM3FHLD28EcVJJ2 > > > > We also got some stack traces those are in there as well. > > > > The way we reproduce it is that on one of the two ceph machines in the = cluster (its a test cluster) we toggle both the bond NIC ports down, sleep = 40 seconds, put them back up, wait another 15 seconds and then put them bac= k down, wait another 40 seconds and=A0=A0 then put them back up. > > > > Exact command line I used on the ceph machine: > > ip l set ens785f1 down; sleep 1 ip l set ens785f0 down; sleep 40; ip l = set ens785f1 up; sleep 5; ip l set ens785f0 up; sleep 15; ip l set ens785f1= down; sleep 1 ip l set ens785f0 down; sleep 40; ip l set ens785f1 up; slee= p 5; ip l set ens785f0 up > > Hi Robin, > > This looks very similar to https://tracker.ceph.com/issues/42757. > I don't see the offending writer thread among stuck threads in > stuck_kthreads.md though (and syslog_stuck_krbd_shrinked covers only > a short 13-second period of time so it's not there either because the > problem, at least the one I'm suspecting, would have occurred before > 13:00:00). > > If you can reproduce reliably, try again without verbose logging but > do capture all stack traces -- once the system locks up, let it stew > for ten minutes and attach "blocked for more than X seconds" splats. > > Additionally, a "echo w >/proc/sysrq-trigger" dump would be good if > SysRq is not disabled on your servers. > > Thanks, > >=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ilya > > > > > Regards, > > > > Robin Geuze > > > > From: Ilya Dryomov > > Sent: 19 April 2021 14:40:00 > > To: Robin Geuze > > Cc: Ceph Development > > Subject: Re: All RBD IO stuck after flapping OSD's > > > > On Thu, Apr 15, 2021 at 2:21 PM Robin Geuze = wrote: > > > > > > Hey Ilya, > > > > > > We had to reboot the machine unfortunately, since we had customers un= able to work with their VM's. We did manage to make a dynamic debugging dum= p of an earlier occurence, maybe that can help? I've attached it to this em= ail. > > > > No, I don't see anything to go on there.=A0 Next time, enable logging f= or > > both libceph and rbd modules and make sure that at least one instance o= f > > the error (i.e. "pre object map update failed: -16") makes it into the > > attached log. > > > > > > > > Those messages constantly occur, even after we kill the VM using the = mount, I guess because there is pending IO which cannot be flushed. > > > > > > As for how its getting worse, if you try any management operations (e= g unmap) on any of the RBD mounts that aren't affected, they hang and more = often than not the IO for that one also stalls (not always though). > > > > One obvious workaround workaround is to unmap, disable object-map and > > exclusive-lock features with "rbd feature disable", and map back.=A0 Yo= u > > would lose the benefits of object map, but if it is affecting customer > > workloads it is probably the best course of action until this thing is > > root caused. > > > > Thanks, > > > >=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ilya > > > > > > > > Regards, > > > > > > Robin Geuze > > > > > > From: Ilya Dryomov > > > Sent: 14 April 2021 19:00:20 > > > To: Robin Geuze > > > Cc: Ceph Development > > > Subject: Re: All RBD IO stuck after flapping OSD's > > > > > > On Wed, Apr 14, 2021 at 4:56 PM Robin Geuze wrote: > > > > > > > > Hey, > > > > > > > > We've encountered a weird issue when using the kernel RBD module. I= t starts with a bunch of OSD's flapping (in our case because of a network c= ard issue which caused the LACP to constantly flap), which is logged in dme= sg: > > > > > > > > Apr 14 05:45:02 hv1 kernel: [647677.112461] libceph: osd56 down > > > > Apr 14 05:45:03 hv1 kernel: [647678.114962] libceph: osd54 down > > > > Apr 14 05:45:05 hv1 kernel: [647680.127329] libceph: osd50 down > > > > (...) > > > > > > > > After a while of that we start getting these errors being spammed i= n dmesg: > > > > > > > > Apr 14 05:47:35 hv1 kernel: [647830.671263] rbd: rbd14: pre object = map update failed: -16 > > > > Apr 14 05:47:35 hv1 kernel: [647830.671268] rbd: rbd14: write at ob= jno 192 2564096~2048 result -16 > > > > Apr 14 05:47:35 hv1 kernel: [647830.671271] rbd: rbd14: write resul= t -16 > > > > > > > > (In this case for two different RBD mounts) > > > > > > > > At this point the IO for these two mounts is completely gone, and t= he only reason we can still perform IO on the other RBD devices is because = we use noshare. Unfortunately unmounting the other devices is no longer pos= sible, which means we cannot migrate=A0=A0 our=A0 VM's to another HV, sinc= e to make the messages go away we have to reboot the server. > > > > > > Hi Robin, > > > > > > Do these messages appear even if no I/O is issued to /dev/rbd14 or on= ly > > > if you attempt to write? > > > > > > > > > > > All of this wouldn't be such a big issue if it recovered once the c= luster started behaving normally again, but it doesn't, it just keeps being= stuck, and the longer we wait with rebooting this the worse the issue get. > > > > > > Please explain how it's getting worse. > > > > > > I think the problem is that the object map isn't locked.=A0 What > > > probably happened is the kernel client lost its watch on the image > > > and for some reason can't get it back.=A0=A0 The flapping has likely > > > trigged some edge condition in the watch/notify code. > > > > > > To confirm: > > > > > > - paste the contents of /sys/bus/rbd/devices/14/client_addr > > > > > > - paste the contents of /sys/kernel/debug/ceph/.client/osdc > > >=A0=A0 for /dev/rbd14.=A0 If you are using noshare, you will have mult= iple > > >=A0=A0 client instances with the same cluster id.=A0 The one you need = can be > > >=A0=A0 identified with /sys/bus/rbd/devices/14/client_id. > > > > > > - paste the output of "rbd status " (image name can be > > >=A0=A0 identified from "rbd showmapped") > > > > > > I'm also curious who actually has the lock on the header object and t= he > > > object map object.=A0 Paste the output of > > > > > > $ ID=3D$(bin/rbd info --format=3Djson / | jq= -r .id) > > > $ rados -p lock info rbd_header.$ID rbd_lock | jq > > > $ rados -p lock info rbd_object_map.$ID rbd_lock | jq > > > > > > Thanks, > > > > > >=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Ilya > > > > > > =