Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Jun 2017 15:35:31 +0200
From:      Raimo Niskanen <raimo+freebsd@erix.ericsson.se>
To:        <freebsd-questions@freebsd.org>
Subject:   Re: Advice on kernel panics
Message-ID:  <20170601133531.GA2256@erix.ericsson.se>
In-Reply-To: <aa54d327-5983-0c2d-1b79-8df736201e30@netfence.it>
References:  <20170529092043.GA89682@erix.ericsson.se> <aa54d327-5983-0c2d-1b79-8df736201e30@netfence.it>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, Jun 01, 2017 at 11:58:48AM +0200, Andrea Venturoli wrote:
> 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.

Good advice, but I should have given more details from the start.
I have only ZFS and NFS filesystems (and devfs andalso fdescfs).

-- 

/ Raimo Niskanen, Erlang/OTP, Ericsson AB



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20170601133531.GA2256>