From owner-freebsd-fs@freebsd.org Tue Mar 1 17:17:58 2016 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 2CC9FABDAF9 for ; Tue, 1 Mar 2016 17:17:58 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8BF5147E for ; Tue, 1 Mar 2016 17:17:57 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5879828429; Tue, 1 Mar 2016 18:17:54 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9731B28439; Tue, 1 Mar 2016 18:17:53 +0100 (CET) Message-ID: <56D5CEC1.2070000@quip.cz> Date: Tue, 01 Mar 2016 18:17:53 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Steven Hartland , freebsd-fs@freebsd.org Subject: Re: abnormally high CPU load after zfs destroy References: <56D4964D.3010604@quip.cz> <56D4B66D.4070007@multiplay.co.uk> In-Reply-To: <56D4B66D.4070007@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2016 17:17:58 -0000 Steven Hartland wrote on 02/29/2016 22:21: > Its likely churning through the actual delete, show system processes in > top and you'll see it. Yes, there are about 300 kernel thread doing ZFS work, but should it really bomb the system that way? The system is heavilly lagging for about 10 minutes. Are there any sysctl to control this behavior? Miroslav Lachman