From owner-freebsd-questions@freebsd.org Fri Oct 5 16:22:11 2018 Return-Path: Delivered-To: freebsd-questions@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 7024D10B09BC for ; Fri, 5 Oct 2018 16:22:11 +0000 (UTC) (envelope-from citrin+bsd@citrin.ru) Received: from hz.citrin.ru (hz.citrin.ru [IPv6:2a01:4f8:d16:10c3::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 913F187010 for ; Fri, 5 Oct 2018 16:22:09 +0000 (UTC) (envelope-from citrin+bsd@citrin.ru) Received: from x220.lan (unknown [IPv6:2601:18a:c680:9888:c901:3cf8:5a21:d5d7]) by hz.citrin.ru (Postfix) with ESMTPSA id B853E2E8916 for ; Fri, 5 Oct 2018 16:22:05 +0000 (UTC) Subject: Re: FreeBSD 11.2 - all processes hang in D state To: freebsd-questions@freebsd.org References: From: Anton Yuzhaninov Openpgp: preference=signencrypt Message-ID: Date: Fri, 5 Oct 2018 12:22:04 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrin.ru; s=s0; t=1538756526; bh=nnoei0qqCgoPqiYsRzrjuHbzrPL9NDvEYIM4PDnrpoU=; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ZcotwkgOHAiH/ewZjwoF6mg4ts1cNa6J4yIxINP12dB64hEOGrBrB44hEIxWigTEXtbWkCQk6MwB0ofpWhFIbFyQi08jHp0HvZED/pkvL3u9NI1ViSTGJZ5id1Zsx1qAyCuMiLB3BEoH9jo8F1Ev3wAwoIvVLCcMulXJHMF1N5E= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2018 16:22:11 -0000 On 10/5/18 4:51 AM, Christos Chatzaras wrote: > The problem is that all processes that are related somehow to /home stuck in D state. > > I was able to shutdown mysql which has the data in /var partition. > > The servers use UFS SU+J but I don't think it's related as they run stable for a long time. There are many reasons why process cat stuck in D state. Most common: - bad HDD. Be sure to run SMART long self-test and examine 'smartctl -a' output. Even better is to run smartd configured to do periodic tests and sned mail in case of failure - some bug in UFS code - some bug in disk controlled driver Suggestions to get more info: 1. top -SH output will be more useful than ps - it will show wait channel for blocked processes. 2. run gstat and check what it will show when problem will happen 3. Configure syslog to forward kernel messages to other host to get full logs. In case of problems with disk/FS not all messages will be written to local /var/log/messages