From owner-freebsd-fs@freebsd.org Wed Jan 4 18:43:12 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 37556C9E5AA for ; Wed, 4 Jan 2017 18:43:12 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-wj0-x22b.google.com (mail-wj0-x22b.google.com [IPv6:2a00:1450:400c:c01::22b]) (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 C24AB1D7A for ; Wed, 4 Jan 2017 18:43:11 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-wj0-x22b.google.com with SMTP id ew7so3796979wjc.3 for ; Wed, 04 Jan 2017 10:43:11 -0800 (PST) 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=CsSubHtYWGIP0D5HMKFKLFu743WfFn+UagvrNGnovZc=; b=GTp5cuXD+qlm2fzcs2SMUnpIrfPf5KK+Zma5BRW/ZzQDkiyATKtS2m3ZTGJG6keQP5 dGKd5iTi/ZlmKy/DbBIwCJR1Gnx/u3YE/5kr0iBkDgo0QXNT+dtlgUpF5zYe3xRB5lD1 m39cActPATTzXxQ7FtLDPAnYlTfZSUezjqIT5BxIzGgpqWq/Oi/K4qk98g9mYX5ezdWH 9OKWNh+x/w/hpSaHalXWeOgDWzH62E5o2kiGo4SpZ4ZCNn5PkUdEdrzYAWMmoRb4u6Dg FLfctyn+PZ7/S39V3Py0VhQKo54qPrP2YC9W/UdhI4F319ISUFn+FjRs39bGTHZY5az+ C7og== 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=CsSubHtYWGIP0D5HMKFKLFu743WfFn+UagvrNGnovZc=; b=dHQzoAeGvf7vLpaNnvqS2T3WPiMzYqthKUCy8WqWKEQ0aJEFzEHx7EpyqgQAsKW3S/ Qalm2CRfloGyEmxcLJ92WSaXttPwOeHpZ1vNIOZOtyFvR2UFkdpPXzoxHMvN2EcFHlRM DOLY6LU99BNMbszqqis1i2Le/StS8AAlBBqXHqMvDac65SI9bevcO4ThrLEXJpmtvjXn 71Q36pBFES1Ldsy3eYHbfT3GRSJLHtSKhnvr1HKAqOq60bxmvHD1abQ6fSPOjrAvZ+ze DhrN6yoQPqHKPiNwucWU1gaxR3X7jRIj9bnFD28hafA8zeGXcDEZ5r+Snh17c+duqr76 Z2fw== X-Gm-Message-State: AIkVDXJMuRRKFxSb7cmtQcPFLmPZlnzYo3XdOiKhzkax3vFSlaebYU+dMBKiXSrL1Zrl026lkyDDDuYAXaJglQ== X-Received: by 10.194.20.34 with SMTP id k2mr58910638wje.9.1483555390128; Wed, 04 Jan 2017 10:43:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.74.100 with HTTP; Wed, 4 Jan 2017 10:43:09 -0800 (PST) In-Reply-To: References: From: Xin LI Date: Wed, 4 Jan 2017 10:43:09 -0800 Message-ID: Subject: Re: Check status of background destroy To: Freddie Cash 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: Wed, 04 Jan 2017 18:43:12 -0000 Try setting vfs.zfs.free_max_blocks to 100000 (this is an arbitrary number, can be larger, limits maximum blocks being freed per txg; see https://svnweb.freebsd.org/base?view=revision&revision=271532 for details). You can inspect the progress with DTrace by looking at zfs-dbgmsg. On Wed, Jan 4, 2017 at 10:30 AM, Freddie Cash wrote: > Is there a way to check the progress of a background destroy process? > > I did a very bad thing in the middle of December. "zfs destroy -r > poolname/dataset", where there's approx 40 TB of data in that dataset, > spread across about 400 snapshots, sitting on a dedupe-enabled pool. :( > (Usually, I delete individual snapshots, but thought I would try a > recursive destroy instead.) > > Needless to say, the 128 GB of RAM in the box, with 128 GB of L2ARC on SSD, > is not enough to hold the DDT, and the box deadlocks after about 8 hours of > disk churning. Once Wired memory goes above 120 GB, the system is > unresponsive to everything, including pings. > > During that 8 hour period, the pool is usable; I can read and write data to > the pool, I can create and destroy snapshots, and I can receive snapshots > from other systems. But the background destroy continues to run after > every boot, continues to churn through RAM, and locks everything up after > about 8 hours. > > This has been going on for several weeks now. > > Is there any way to check the progress of the background destroy to see how > much longer this will continue, how much data has been freed, how much of > the DDT has been updated, etc? "zfs list" shows very little change in free > space. > > Or am I just going to have to live with resetting the box every 8-10 hours > for the next few weeks? Unfortunately, adding more RAM to the box isn't an > option right now. :( > > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >