From nobody Tue Aug 15 16:26:19 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 4RQGqJ60Vbz4q6vw for ; Tue, 15 Aug 2023 16:26:20 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oo1-xc2e.google.com (mail-oo1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (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 4RQGqJ3zGsz4X3G; Tue, 15 Aug 2023 16:26:20 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-56d6dfa8b52so3877764eaf.3; Tue, 15 Aug 2023 09:26:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692116779; x=1692721579; 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=6gOs2Ul666Gfp6aOQ2AF13jY6Bg4mR2vDPAa746aL10=; b=UoAf+a13+ag8pDHx97ZhPoe2DsvDM6zN6aT7no1UeaiL85xZMNw8qNLIMEVtpjXl7c ssMnjWfwcvtNNResZQCv2hjtdPQbRpMtm4MhZSaJT8dhBfoyytR1bCauFI85795rvN82 9on7AACh+vLtAT45BJXEKOXntZNDc1ABW+N4nbwFGSuPEjjrKAqH0p4ajs71Op3i3YO8 gFOgLBUBiLMuqWzb/3se308hIgDl0WBUH2dPupNYLCIglWF5W5AHNnpX1ZUaMHJ7JaFN nB4AB8s93H0oH8gkV4r175C2AdK2We9DRAmnEwnVfXCNF24obCjl7d0IeBHyD6Judv3U zbuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692116779; x=1692721579; 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=6gOs2Ul666Gfp6aOQ2AF13jY6Bg4mR2vDPAa746aL10=; b=Il6gOj/bO2gHPGcgtBPSgIpxuQ6WVOJ3zxy69GwgubJqsv5wrrBDjkUT9yOuJ94/1d 0PCVlYN85lITTK6f3VA36/iofpX/z0SVuG+qxbxs1mRxKiWo9nH9aZ5S7+aOu4A6ea1i JIgQpc2KNZACO+xaRuT9sle0FVingUpKGvz+YJEHnrgFVzx2+fbL9y5LdCrzHAocEKH8 3NuI/rH6evb93nu7teg5aF9ogAQcLgGkrCJWFQTjtpkkSliZgvLoeh1Y0SJUcR6Korvs U/7mWiw7gmJDOfaSbYUtyN/LAoiNefO5X4zhJqSz5qrECKsfE0ctjmexMIECeoUvXg0L y7Aw== X-Gm-Message-State: AOJu0YwNlyKDCMIsXmGbCovpv2nGlY5zU/AEOv8q54o0CcBqxCOKaBU5 +v6Wv9ecYpjlw+m8EpZvEgPcsKbXOGX/fwInqb+lXR1wnrE= X-Google-Smtp-Source: AGHT+IHUsiiKpLYgiX+v417ugU4yYFwwabyCQ/PEhAFNKL+mtKRNGHKZQf+7KFUUwkpd+fWSDLydQdXp0oc9TIivbqA= X-Received: by 2002:a05:6870:61cc:b0:1ad:e92:62e1 with SMTP id b12-20020a05687061cc00b001ad0e9262e1mr13447873oah.54.1692116779641; Tue, 15 Aug 2023 09:26:19 -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:26:19 -0700 (PDT) In-Reply-To: <86y1icp95t.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> <86y1icp95t.fsf@ltc.des.no> From: Mateusz Guzik Date: Tue, 15 Aug 2023 18:26:19 +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: 4RQGqJ3zGsz4X3G 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: > Mateusz Guzik writes: >> 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. > > Why? What more information do you need? > Going through the list may or may not reveal other threads doing something in the area and it very well may be they are deadlocked, which then results in other processes hanging on them. Just like in your case the process reported as hung is a random victim and whatever the real culprit is deeper. --=20 Mateusz Guzik