From owner-freebsd-fs@freebsd.org Thu Oct 5 05:28:29 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ECEDE2D050 for ; Thu, 5 Oct 2017 05:28:29 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E288772 for ; Thu, 5 Oct 2017 05:28:29 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-oi0-x236.google.com with SMTP id m198so10590940oig.5 for ; Wed, 04 Oct 2017 22:28:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kUPdpCOvjQduzMZ3nhzx5yg/fz9DMvC2L/IIH/O8n/0=; b=Uvi3I8J5oKWWZ8+4oVA9t26GMuFkqdxqStL+gW8M6cVRyNpg3yLt/dxUGCKHzgl/TR BbIljYqTUd3ZlAOT03EvZYIcNHFsHpx/OHKjSpD7MbOaWLHswAaDlRzVg2a/HB8lrI4V cfmBVfU1hJiZVEHcT99D/ac8PWayQrErrXcWdc4m0qCHBA9K9/EKyPJyC5wss7yhtaUt a8glMQU81ZIZdmmxEBcOwSqJ63xaAU2ZkjQvulR5z0W+caGLHgVOVldJfqauQc6pkCSt n1F3NtRFus8HPowhlwy4098FGOS5bw2Xx0JE8Qg9e6IENpueSZD5iZEBFzmL9gDFw8Hb DTYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kUPdpCOvjQduzMZ3nhzx5yg/fz9DMvC2L/IIH/O8n/0=; b=SqrBdXetnttf3P4Kqdd4PcL652JNLRUSw6Uby937ynbI7U9UeRlUQm2nPB53C90cgm DIdIw30hptjMdBnGblQvDUb+PmMr/iMVgX/RVyeT3iIn+l+RV4LdrIT1q1ZO6oGvUuXe CR2DfBsJ6BiZ8GQXAKL7ygc5GYGme0mGh5kHfXbm5vejHB26kH1F56mweWpkw6muXnZb YFFse83XSoc40hcD9odAPF9rgjxoWdfrkg74cjCQfGfHjrrEz6wEkh2sLv9tKKb5aG6l 2+DdyCLFiMNeGzzwT56cuPo+obHDg7yugG+wILwLNr2f66IqXorVbb7YVhXrHtK/FgOB UeTw== X-Gm-Message-State: AMCzsaWbsfUR/0NobeVhcBQGfkD4RT2zqa7XfYFdr6wryVVg2KWKjIrb 17x6UxOye/OXfSLPjBXCdZq7mcne34VtxahjSnE= X-Google-Smtp-Source: AOwi7QCNat2R1CCwbxc7SoPOHZcpGBP9RKDrjARe6f1dBToxEsH2DTMvvdCGBf7kj/iGwIzzruI4BzpOEoSFfEFQmr4= X-Received: by 10.157.45.107 with SMTP id v98mr9773483ota.133.1507181308371; Wed, 04 Oct 2017 22:28:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.62.245 with HTTP; Wed, 4 Oct 2017 22:28:27 -0700 (PDT) Received: by 10.157.62.245 with HTTP; Wed, 4 Oct 2017 22:28:27 -0700 (PDT) In-Reply-To: References: From: Freddie Cash Date: Wed, 4 Oct 2017 22:28:27 -0700 Message-ID: Subject: Re: lockup during zfs destroy To: javocado Cc: FreeBSD Filesystems Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 05:28:29 -0000 On Oct 4, 2017 10:13 PM, "javocado" wrote: Setting vfs.zfs.free_max_blocks to 20k has not helped unfortunately. No, that won't help with this issue as the destroy operation is already in progress and part of a transaction group. But it will mitigate or (hopefully) prevent this issue in the future. Cheers, Freddie