From owner-freebsd-questions@freebsd.org Thu Jun 1 10:05:17 2017 Return-Path: Delivered-To: freebsd-questions@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 98837AF8365 for ; Thu, 1 Jun 2017 10:05:17 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp209.alice.it (smtp209.alice.it [82.57.200.105]) by mx1.freebsd.org (Postfix) with ESMTP id 2FC6F7396B for ; Thu, 1 Jun 2017 10:05:16 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.26.54.44) by smtp209.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 58D1259E37A64AF7 for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 11:58:48 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v519wmPp082568 for ; Thu, 1 Jun 2017 11:58:48 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Advice on kernel panics To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> From: Andrea Venturoli Message-ID: Date: Thu, 1 Jun 2017 11:58:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170529092043.GA89682@erix.ericsson.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 10:05:17 -0000 On 05/29/17 11:20, Raimo Niskanen wrote: > Hello list. > > I have a server that panics about every 3 days and need some advice on how > to handle that. As Doug suggested, it's probably an hardware fault. However, I've many times seen boxes crash every day or two when an UFS+SU filesystem gets corrupted. Background fsck won't detect this. In order to stop the crashes, I always had to boot into single user mode and do a fsck -y (twice if asked) on every UFS+SU filesystem. Furthermore, if you are using SU+J, you'll have to run fsck first to deal with the journal and then fsck it again (ignoring the journal). This has brought several boxes I manage back on track on many occasions. You might want to try this, since the only downside is downtime. HTH. bye av.