Date: Tue, 12 Dec 2017 19:05:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224292] processes are hanging in state ufs / possible deadlock in file system Message-ID: <bug-224292-8-6KDQFhUZLk@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224292-8@https.bugs.freebsd.org/bugzilla/> References: <bug-224292-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224292 --- Comment #1 from Wolfram Schneider <wosch@FreeBSD.org> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224292-8-6KDQFhUZLk>