From nobody Tue Aug 15 16:21:41 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RQGk03g2fz4q6RD for ; Tue, 15 Aug 2023 16:21:44 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oo1-xc2c.google.com (mail-oo1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RQGk01Fzcz4Tp8; Tue, 15 Aug 2023 16:21:44 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-56d6879dcaaso4061979eaf.3; Tue, 15 Aug 2023 09:21:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692116502; x=1692721302; h=content-transfer-encoding:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=wvTRrgE6qE0O3dV7oIPRQ3Jy+jKoMqKaQAVe/lf08ao=; b=CnCxzkjwGfkqb4aL5Vg5EvP72IToxkFq52HkwtcwJ8Bt8hquBg+Ycl/W63qKxz+BRX AbgqdJCM+O8dTPyQHWHdr44k8Y7DMUjBpvHRuEKqj+QsZJnk9+EoVUCk0LLX0PrvN3PN Gu47/tQebyOSthren/InGpyEPOjjUa4bnXBT92BZT2uyGMn7O765kisu2QTpeCHdREOs VForMqcL336OhaWCSlDfWOhHwxTeHibJBXlcOEDi4QgpYZUeItJws22NboAowu107IRi gDUtFCFvQXuOA7Rkqu8KSsA5WQWBDu98bV+mu64ML2sQ6snXd28GAajdPupmfQIDloUN ssng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692116502; x=1692721302; h=content-transfer-encoding:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wvTRrgE6qE0O3dV7oIPRQ3Jy+jKoMqKaQAVe/lf08ao=; b=cLDVZ9GiE5klQOtoxjlKspO56Py0C4FwAVdCl4DHNCFs/ZbBMzhtcmcAtHHfE93LLF btX3/pbEjKuzqWWGnkLwgGNSIX7BiFvrTHYaZ46rExmunTcHYikGpCIwY3Szz/ShTYyT q7tLwvjBGmCZNj/8i74QFY3jloAeGgUvtYc4/4UtFtJAxIOUaqv7LF32sXx7+ElQaz4Y ahvOVGylhRoccPnBN9Yq3VYrBk5BrFUXLQjTCs4OaQyvfRE5w+c+bhBdxTptxIrfQ5t/ JjZuWiT0ZeaZd28ORG7g63PKfCOnqIoLLhmx64vjAOzwB9Rb21zpS78xdx0F6bD4uHbF j1XA== X-Gm-Message-State: AOJu0YxR0+AiitcWQBnrJokW6YmuJuJYnkvFDrJzVji06VGP7RBbJ5vn ffjVzhhGWCqjCStc/GOE4LYTQZXuMmeBDL1yzUkXzU7cAHQ= X-Google-Smtp-Source: AGHT+IEf3yieWi8wEMpcDyTFYGs4sy4tAI1FLMwXTUm+Uh4xR59GvM+bTaSWTW0Wn3nJZrUeB3U+WbYL5npSS3C/mjU= X-Received: by 2002:a4a:9d57:0:b0:56e:14b7:b053 with SMTP id f23-20020a4a9d57000000b0056e14b7b053mr7452470ook.7.1692116502360; Tue, 15 Aug 2023 09:21:42 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: by 2002:ac9:745a:0:b0:4f0:1250:dd51 with HTTP; Tue, 15 Aug 2023 09:21:41 -0700 (PDT) In-Reply-To: <86350kqokl.fsf@ltc.des.no> References: <86leeltqcb.fsf@ltc.des.no> <86h6p4s64h.fsf@ltc.des.no> <86a5utrafp.fsf@ltc.des.no> <86350kqokl.fsf@ltc.des.no> From: Mateusz Guzik Date: Tue, 15 Aug 2023 18:21:41 +0200 Message-ID: Subject: Re: ZFS deadlock in 14 To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= Cc: current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4RQGk01Fzcz4Tp8 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On 8/15/23, Dag-Erling Sm=C3=B8rgrav wrote: > Dag-Erling Sm=C3=B8rgrav writes: >> I managed to geat a deadlock with 4e8d558c9d1c. Its predecessor >> 5ca7f02946 appears to be working. I'm going to try to come up with a >> more efficient way to reproduce the deadlock than running poudriere. > > I wrote a script that creates multiple filesystems, snapshots them, > populates them and rolls them back continuously but so far I have not > succeeded in triggering the deadlock without poudriere. I guess my > script doesn't consume enough vnodes. > > Also, 9228ac3a69c4 (9 August, last commit before the contrib/googletest > breakage) still deadlocks. > Given that the custom reproducer failed I think the most prudent course of action is to reproduce again with poudriere, but this time arrange to have all stacktraces dumped. this should do it: sbin/ddb/ddb.conf:script kdb.enter.panic=3Dtextdump set; capture on; run lockinfo; show pcpu; bt; ps; alltrace; capture off; textdump dump; reset it is a slightly finicky beast so I would trigger a panic by hand first to validate it works as expected. --=20 Mateusz Guzik