From owner-freebsd-stable@FreeBSD.ORG Sat May 2 18:46:33 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28901247 for ; Sat, 2 May 2015 18:46:33 +0000 (UTC) Received: from j006.host001.searchy.nl (j006.host001.searchy.nl [79.143.214.199]) by mx1.freebsd.org (Postfix) with ESMTP id E4E4616AE for ; Sat, 2 May 2015 18:46:32 +0000 (UTC) Received: from [192.168.5.21] (5418287B.cm-5-1a.dynamic.ziggo.nl [84.24.40.123]) (Authenticated sender: ppi@j006.host001.searchy.nl) by j006.host001.searchy.nl (Postfix) with ESMTPSA id 46A221E8C4C for ; Sat, 2 May 2015 18:37:22 +0000 (UTC) Message-ID: <55451961.5070708@searchy.net> Date: Sat, 02 May 2015 20:37:21 +0200 From: "Frank de Bot (lists)" User-Agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: kernel process [nfscl] high cpu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2015 18:46:33 -0000 Hi, On a 10.1-RELEASE-p9 server I have several NFS mounts used for a jail. Because it's a server only to test, there is a low load. But the [nfscl] process is hogging a CPU after a while. This happens pretty fast, within 1 or 2 days. I'm noticing the high CPU of the process when I want to do some test after a little while (those 1 or 2 days). My jail.conf look like: exec.start = "/bin/sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; exec.clean; mount.devfs; exec.consolelog = "/var/log/jail.$name.log"; #mount.fstab = "/usr/local/etc/jail.fstab.$name"; test01 { host.hostname = "test01_hosting"; ip4.addr = somepublicaddress; ip4.addr += someprivateaddress; mount = "10.13.37.2:/tank/hostingbase /opt/jails/test01 nfs nfsv4,minorversion=1,pnfs,ro,noatime 0 0"; mount += "10.13.37.2:/tank/hosting/test /opt/jails/test01/opt nfs nfsv4,minorversion=1,pnfs,noatime 0 0"; path = "/opt/jails/test01"; } Last test was with NFS 4.1, I also worked with NFS 4.(0) with the same result. In the readonly nfs share there are symbolic links point to the read-write share for logging, storing .run files, etc. When I monitor my network interface with tcpdump, there is little nfs traffic, only when I do try to access the shares there is activity. What is causing nfscl to run around in circles, hogging the CPU (it makes the system slow to respond too) or how can I found out what's the cause? Regards, Frank de Bot