From owner-freebsd-questions@freebsd.org Mon Nov 16 10:48:58 2015 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 43D85A26298 for ; Mon, 16 Nov 2015 10:48:58 +0000 (UTC) (envelope-from schmidt@ze.tum.de) Received: from io.ze.tum.de (w3projmail.ze.tum.de [129.187.39.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C46191C34 for ; Mon, 16 Nov 2015 10:48:56 +0000 (UTC) (envelope-from schmidt@ze.tum.de) Received: from etustar.ze.tum.de (etustar.ze.tum.de [129.187.39.200]) by io.ze.tum.de (8.14.5/8.14.5) with ESMTP id tAGAmsg8069409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 16 Nov 2015 11:48:54 +0100 (CET) (envelope-from schmidt@ze.tum.de) Resent-From: Gerhard Schmidt Resent-To: freebsd-questions@freebsd.org Resent-Date: Mon, 16 Nov 2015 11:48:54 +0100 Resent-Message-ID: <5649B496.7000705@ze.tum.de> Resent-User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 Subject: Re: Random Lockup with FreeBSD 10.2 on SuperMicro Boards To: Polytropon References: <56498205.3060806@ze.tum.de> <20151116094334.GS2604@mordor.lan> <5649A761.7040303@ze.tum.de> <20151116111609.a9757a4a.freebsd@edvax.de> From: Gerhard Schmidt X-Enigmail-Draft-Status: N1110 Message-ID: <5649AEC3.5090104@ze.tum.de> Date: Mon, 16 Nov 2015 11:24:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151116111609.a9757a4a.freebsd@edvax.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 10:48:58 -0000 Am 16.11.2015 um 11:16 schrieb Polytropon: > On Mon, 16 Nov 2015 10:52:33 +0100, Gerhard Schmidt wrote: >> My Workstation is running 10.2 for about at least 4 Month. I've never >> had a problem event with SU+J. The difference is that on my workstation >> /var is not on a raid array. So SU+J isn't the real problem. > > Maybe there's a file system inconsistency? How do you > perform file system checks (automatic in background, > which is discouraged, or in SUM, as recommended)? > I'm asking because I've noticed the following lines > in your previous message: > >> Trying to mount root from ufs:/dev/raid/r0p3 [rw]... >> WARNING: / was not properly dismounted > > Is /var affected as well? If yes - give it a _clean_ > fsck, running in foreground on the unmounted partition. > > In case you have already done this, redirect my comment > to /dev/null immediately. :-) /var was also inconsistent because of the lockup, I had to turn off the server hard. The fsck recovered the Journal and marked the fs as clean without background fsck. Nov 16 07:15:40 dev-test-zope kernel: ** SU+J Recovering /dev/raid/r0p4 Nov 16 07:15:40 dev-test-zope kernel: ** Reading 33554432 byte journal from inode 4. Nov 16 07:15:40 dev-test-zope kernel: ** Building recovery table. Nov 16 07:15:40 dev-test-zope kernel: ** Resolving unreferenced inode list. Nov 16 07:15:40 dev-test-zope kernel: ** Processing journal entries. Nov 16 07:15:40 dev-test-zope kernel: ** 2 journal records in 1024 bytes for 6.25% utilization Nov 16 07:15:40 dev-test-zope kernel: ** Freed 0 inodes (0 dirs) 0 blocks, and 0 frags. Nov 16 07:15:40 dev-test-zope kernel: Nov 16 07:15:40 dev-test-zope kernel: ***** FILE SYSTEM MARKED CLEAN ***** Regards Estartu -- ------------------------------------------------- Gerhard Schmidt | E-Mail: schmidt@ze.tum.de TU-München | Jabber: estartu@ze.tum.de WWW & Online Services | Tel: 089/289-25270 | Fax: 089/289-25257 | PGP-Publickey auf Anfrage