From owner-freebsd-stable@freebsd.org Wed Nov 9 13:58:30 2016 Return-Path: Delivered-To: freebsd-stable@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 3D854C383E5 for ; Wed, 9 Nov 2016 13:58:30 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id 295D3B1E for ; Wed, 9 Nov 2016 13:58:29 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from ford.home.vangyzen.net (unknown [76.164.15.242]) by smtp.vangyzen.net (Postfix) with ESMTPSA id AE7855648E; Wed, 9 Nov 2016 07:58:23 -0600 (CST) Subject: Re: Freebsd 11.0 RELEASE - ZFS deadlock To: freebsd-stable@freebsd.org, Henri Hennebert References: <0c223160-b76f-c635-bb15-4a068ba7efe7@restart.be> From: Eric van Gyzen Message-ID: Date: Wed, 9 Nov 2016 07:58:20 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <0c223160-b76f-c635-bb15-4a068ba7efe7@restart.be> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2016 13:58:30 -0000 On 11/09/2016 07:48, Henri Hennebert wrote: > I encounter a strange deadlock on > > FreeBSD avoriaz.restart.bel 11.0-RELEASE-p3 FreeBSD 11.0-RELEASE-p3 #0 r308260: > Fri Nov 4 02:51:33 CET 2016 > root@avoriaz.restart.bel:/usr/obj/usr/src/sys/AVORIAZ amd64 > > This system is exclusively running on zfs. > > After 3 or 4 days, `periodic daily` is locked in the directory /usr/local/news/bin > > [root@avoriaz ~]# ps xa|grep find > 85656 - D 0:01.13 find / ( ! -fstype local -o -fstype rdonly ) -prune > -o ( -name [#,]* -o -name .#* -o -name a.out -o -nam > 462 1 S+ 0:00.00 grep find > [root@avoriaz ~]# procstat -f 85656 > PID COMM FD T V FLAGS REF OFFSET PRO NAME > 85656 find text v r r------- - - - /usr/bin/find > 85656 find cwd v d r------- - - - /usr/local/news/bin > 85656 find root v d r------- - - - / > 85656 find 0 v c r------- 3 0 - /dev/null > 85656 find 1 p - rw------ 1 0 - - > 85656 find 2 v r -w------ 7 17 - - > 85656 find 3 v d r------- 1 0 - /home/root > 85656 find 4 v d r------- 1 0 - /home/root > 85656 find 5 v d r----n-- 1 533545184 - /usr/local/news/bin > [root@avoriaz ~]# > > If I try `ls /usr/local/news/bin` it is also locked. > > After `shutdown -r now` the system remain locked after the line '0 0 0 0 0 0' > > After a reset and reboot I can access /usr/local/news/bin. > > I delete this directory and reinstall the package `portupgrade -fu news/inn` > > 5 days later `periodic daily`is locked on the same directory :-o > > Any idea? I can't help with the deadlock, but someone who _can_ help will probably ask for the output of "procstat -kk PID" with the PID of the "find" process. Eric