From owner-freebsd-current@FreeBSD.ORG Wed May 19 11:15:00 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C9A41065678 for ; Wed, 19 May 2010 11:14:50 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E95E58FC08 for ; Wed, 19 May 2010 11:14:49 +0000 (UTC) Received: by mail-pw0-f54.google.com with SMTP id 9so4095101pwi.13 for ; Wed, 19 May 2010 04:14:49 -0700 (PDT) Received: by 10.141.2.4 with SMTP id e4mr6179837rvi.60.1274267598522; Wed, 19 May 2010 04:13:18 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id b12sm6082803rvn.22.2010.05.19.04.13.16 (version=SSLv3 cipher=RC4-MD5); Wed, 19 May 2010 04:13:17 -0700 (PDT) Date: Wed, 19 May 2010 01:13:12 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Roman Bogorodskiy In-Reply-To: <20100518185201.GA2745@fsol> Message-ID: References: <20100518185201.GA2745@fsol> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 May 2010 11:15:00 -0000 On Tue, 18 May 2010, Roman Bogorodskiy wrote: > Hi, > > I've been using -CURRENT last update in February for quite a long time > and few weeks ago decided to finally update it. The update was quite > unfortunate as system became very unstable: it just hangs few times a > day and panics sometimes. > > Some things can be reproduced, some cannot. Reproducible ones: > > 1. background fsck always makes system hang > 2. system crashes on operations with nullfs mounts (disabled that for > now) > > The most annoying one is ffs_copyonwrite panic which I cannot reproduce. > The thing is that if I will run 'startx' on it with some X apps it will > panic just in few minutes. When I leave the box with nearly no stress > (just use it as internet gateway for my laptop) it behaves a little > better but will eventually crash in few hours anyway. This may have been my fault. Can you please update and let me know if it is resolved? There was both a deadlock and a copyonwrite panic as a result of the softupdates journaling import. I just fixed the deadlock today. Thanks, Jeff > > The even more annoying thing is that when I cannot save the dump, > because when the system boots and runs 'savecore' it leads to > fss_copyonwrite panic as well. The panic happens when about 90% complete > (as seem via ctrl-t). > > Any ideas how to debug and get rid of this issue? > > System arch is amd64. I don't know what other details could be useful. > > Roman Bogorodskiy >