From owner-freebsd-fs@FreeBSD.ORG Sun Nov 18 02:15:22 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F534BF for ; Sun, 18 Nov 2012 02:15:22 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 994FB8FC08 for ; Sun, 18 Nov 2012 02:15:21 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so1070204lbb.13 for ; Sat, 17 Nov 2012 18:15:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tpa5fNWvLZl96ElcEWuEbpTYNLPH4ZPqcM3rc6A+1SI=; b=NL9u6B5/zm8VaUMxx1xdYTGJYVCLECGjAWRPbqCTfuowxhS3VJPTEZ6cO8pCLHH6Qb Qk87ZI0EnImVUA8/3n1+I6khlFyiwrtlIuWGMPe+HmmpliU72gpdtyoZFTn20rk7zE2A 9oOCndi2BxdBWd4f7A/ti5icDmLSohMmz0eW8/kRtEFwAWpoCVSKRPlXngdxMP8vQ55+ fQtSgnUZjKN923b2MdGgmRAaOzOQkiW3GkmTVkTgNpjcggukr0oDl44aeTAUdrVh7TAh e00HXMHlgWaCo7SohAn54pAQXkBdjfQV0LVQ3u0ewQRnUDTP/B8nf7sxMwNPjVvBhm3t 21Kg== MIME-Version: 1.0 Received: by 10.152.129.197 with SMTP id ny5mr8110106lab.43.1353204920533; Sat, 17 Nov 2012 18:15:20 -0800 (PST) Received: by 10.112.49.138 with HTTP; Sat, 17 Nov 2012 18:15:20 -0800 (PST) In-Reply-To: <20121117225851.GJ1462@egr.msu.edu> References: <57ac1f$gf3rkl@ipmail05.adl6.internode.on.net> <50A31D48.3000700@shatow.net> <20121116044055.GA47859@neutralgood.org> <50A64694.5030001@egr.msu.edu> <20121117181803.GA26421@neutralgood.org> <20121117225851.GJ1462@egr.msu.edu> Date: Sat, 17 Nov 2012 21:15:20 -0500 Message-ID: Subject: Re: SSD recommendations for ZFS cache/log From: Zaphod Beeblebrox To: Adam McDougall Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 02:15:22 -0000 On Sat, Nov 17, 2012 at 5:58 PM, Adam McDougall wrote: > Some found a way to measure progress and kept letting it churn/deadlock/reboot > until things came back to normal. I think in -current there is a new zfs > feature allowing for background deletion that may ease this issue, and > someone reported success. I think the "feature" you're thinking about is the background deletion of a filesystem object. As I recall the problem, the deletion of a filesystem object is atomic ... and can hang a whole array while it happens (I suppose this is doubly true if the filesystem is deduped). The patch makes this happen in the background. However... it wouldn't have any effect on removing a non-filesystem chuck of data, AFAIK. In my experience of copying 1T of data and then recopying that same 1T of data, the first copy took some hours and the 2nd copy took some days. The first delete took many days and the 2nd delete was fairly quick.