From owner-freebsd-stable@FreeBSD.ORG Tue Dec 25 21:16:06 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EEF94383; Tue, 25 Dec 2012 21:16:06 +0000 (UTC) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (mail.takeda.tk [74.0.89.210]) by mx1.freebsd.org (Postfix) with ESMTP id BD39D8FC12; Tue, 25 Dec 2012 21:16:06 +0000 (UTC) Received: from localhost.takeda.tk (takeda-ws2.lan [10.0.0.123]) (authenticated bits=0) by chinatsu.takeda.tk (8.14.5/8.14.5) with ESMTP id qBPLG58K022933 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 25 Dec 2012 13:16:05 -0800 (PST) (envelope-from takeda@takeda.tk) Date: Tue, 25 Dec 2012 13:06:35 -0800 From: Derek Kulinski X-Priority: 3 (Normal) Message-ID: <1501851114.20121225130635@takeda.tk> To: Andriy Gapon Subject: Re: FreeBSD 9.1-RELEASE crashes almost daily; backtraces always list zfs routines In-Reply-To: <50D9614F.6040306@FreeBSD.org> References: <1824023197.20121223142308@takeda.tk> <50D87C56.70709@FreeBSD.org> <331959998.20121224101719@takeda.tk> <50D8E500.1070408@FreeBSD.org> <574019558.20121224161156@takeda.tk> <50D9614F.6040306@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.6 at chinatsu.takeda.tk X-Virus-Status: Clean Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Dec 2012 21:16:07 -0000 Hello Andriy, Tuesday, December 25, 2012, 12:18:23 AM, you wrote: >> I recompiled the kernel and is running with options you specified (I >> enabled DEBUG in the file). >> >> Anyway even at boot time I started getting following warnings, is this >> anything: > These witness warning are OK-ish. > Watch for panics. Sadly (I guess :) I did not have crash today (I don't see even a warning at that time), I'll update when it happens. Will also try to run that task today and will see if it will do anything. > BTW, I should have said this earlier. Whatever the kind of the corruptions it > would be much worse if a corruption would get propagated to the stable storage. > Especially if it would be in any kind of pool metadata. > So, your data is at great risk now. > Please also take measures to back it up. Preferably by using a different system. I'm backing it up using zfs send since dump doesn't appear to work on ZFS. Anyway zpool scrub does not show any problems... I performed my last scan when I started this thread. -- Best regards, Derek mailto:takeda@takeda.tk Hand over the calculator, friends don't let friends derive drunk