From owner-freebsd-bugs@freebsd.org Tue Dec 12 19:05:00 2017 Return-Path: Delivered-To: freebsd-bugs@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 740A8E804FE for ; Tue, 12 Dec 2017 19:05:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 615386C4D3 for ; Tue, 12 Dec 2017 19:05:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBCJ500A008115 for ; Tue, 12 Dec 2017 19:05:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224292] processes are hanging in state ufs / possible deadlock in file system Date: Tue, 12 Dec 2017 19:05:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wosch@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 19:05:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224292 --- Comment #1 from Wolfram Schneider --- I googled for similar bug reports and found this: from 2007, for FreeBSD 6.x https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D104406 kern/104406: Processes get stuck in "ufs" state under persistent CPU load https://forums.freebsd.org/threads/9150/ We have a problem with FreeBSD 6.2-STABLE (aw62) #2: Fri Jun 22 02:26:27 MSD 2007 some reports about dirhash tuning: https://forums.freebsd.org/threads/7794/ Try something like procstat -f -w 1 pid_of_httpd or run top -U www -m io to= see disk activity. I ran into same, in our case it the solution was dirhashing: sysctl -a | grep dirhash will show you current state, and most likely increasing vfs.ufs.dirhash_max= mem will solve your problems.=20=20=20=20=20=20 sysctl -a | grep mem https://wiki.freebsd.org/WaitChannels ufs: Waiting to read from a file or directory on a UFS filesystem that is b= eing written to by another thread, or waiting to write to a local file or direct= ory that is being read or written by another thread=20 https://wiki.freebsd.org/DirhashDynamicMemory https://forums.freebsd.org/threads/34023/ Since vfs.ufs.dirhash_lowmemcount is already at 25, you should consider increase vfs.ufs.dirhash_maxmem. --=20 You are receiving this mail because: You are the assignee for the bug.=