From nobody Tue Aug 08 17:16:47 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 4RL0H24wsQz4prG6 for ; Tue, 8 Aug 2023 17:17:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f48.google.com (mail-ot1-f48.google.com [209.85.210.48]) (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 4RL0H21KXCz4MTk; Tue, 8 Aug 2023 17:17:02 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ot1-f48.google.com with SMTP id 46e09a7af769-6bd0a0a6766so536452a34.2; Tue, 08 Aug 2023 10:17:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691515019; x=1692119819; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=c0yW+5tIPVKPohwVZExSP6qYZMcgXzpHakEQbmOO0Fo=; b=P18MxmkfNgoi8AE6+IM0BagJqjLMUns4K0QpLzAay9RyqjMP8B/kDclEyznnP7sJP8 hhna/RET+sT+ohuOWxFmh+PUd6E/vIlgW1hHBpD0HuWIgg/hUSNVkXW+oqrTkpN5m/u3 /5cehEpeSxfH0k+Xjob5HwNlUXl7TjbAmI27NBnQzETXI5qgya80nArCxOn2wWR9aLA7 nYiDY2UmNodn/JmVZPiAaZl58aJoIoGr0ZeoemdoFS2S+Iuif6ihGbRaPoVfRuMFj4pY BC37RKdJ029QWzYiOtFJaTDr/8rdQl3CK9l00+7jtY3j2+wL8zGTdI5JCi2tUnWPP1wl Z6wg== X-Gm-Message-State: AOJu0YzoiX1OmPCnl4lRXcyuFEtPpPqSMsjD0JvbQH4+D9dkUTprZciO TO2qMZFkn/Fs2Zob9iNbep0/ri4fQr5wkBhDzJZ8UYAYTM0= X-Google-Smtp-Source: AGHT+IGW4FygXBSZOIDeks/VFe31cS8OVSl4ZHX8u7VxYQAYGMYljSZhX/bas7VtZAbhMzhqLi8c2RdD8lCUGJkSBMU= X-Received: by 2002:a05:6358:7e05:b0:134:d128:9f5f with SMTP id o5-20020a0563587e0500b00134d1289f5fmr45847rwm.9.1691515018972; Tue, 08 Aug 2023 10:16:58 -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 References: <86leeltqcb.fsf@ltc.des.no> In-Reply-To: <86leeltqcb.fsf@ltc.des.no> From: Alan Somers Date: Tue, 8 Aug 2023 10:16:47 -0700 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: 4RL0H21KXCz4MTk 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:209.85.128.0/17, country:US] On Tue, Aug 8, 2023 at 10:08=E2=80=AFAM Dag-Erling Sm=C3=B8rgrav wrote: > > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4 > August) and is 100% reproducable just by starting poudriere bulk in a > 16-core VM and waiting a few hours until deadlkres kicks in. In the > latest instance, deadlkres complained about a bash process: Do you have ZFS block cloning enabled on your pool? There were a lot of bugs associated with that feature. I think that was merged on 3-April. > zpool get feature@block_cloning zroot NAME PROPERTY VALUE SOURCE zroot feature@block_cloning disabled local