From owner-freebsd-current@freebsd.org Tue Apr 24 23:30:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60FCCFB6E65 for ; Tue, 24 Apr 2018 23:30:36 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E1287794B6 for ; Tue, 24 Apr 2018 23:30:35 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from lrrr.mouf.net (cpe-2606-A000-4102-2500-6245-CBFF-FE5F-6C74.dyn6.twc.com [IPv6:2606:a000:4102:2500:6245:cbff:fe5f:6c74]) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id w3ONUSkE063221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 24 Apr 2018 23:30:34 GMT (envelope-from swills@FreeBSD.org) To: FreeBSD Current From: Steve Wills Subject: zfskern{txg_thread_enter} thread using 100% or more CPU Message-ID: Date: Tue, 24 Apr 2018 19:30:22 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]); Tue, 24 Apr 2018 23:30:34 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 23:30:36 -0000 Hi, Recently on multiple systems running CURRENT, I've been seeing the system become unresponsive. Leaving top(1) running has lead me to notice that when this happens, the system is still responding to ping and top over ssh is still working, but no new processes can start and switching to other tasks doesn't work. In top, I do see pid 17, [zfskern{txg_thread_enter}] monopolizing both CPU usage and disk IO. Any ideas how to troubleshoot this? It doesn't appear to be a hardware issue. Steve