From owner-freebsd-current@FreeBSD.ORG Mon May 24 03:46:35 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 A70AB1065672 for ; Mon, 24 May 2010 03:46:35 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 845578FC15 for ; Mon, 24 May 2010 03:46:35 +0000 (UTC) Received: by pxi7 with SMTP id 7so1532016pxi.13 for ; Sun, 23 May 2010 20:46:35 -0700 (PDT) Received: by 10.143.26.3 with SMTP id d3mr3314388wfj.232.1274672794999; Sun, 23 May 2010 20:46:34 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id x34sm752850wfi.16.2010.05.23.20.46.33 (version=SSLv3 cipher=RC4-MD5); Sun, 23 May 2010 20:46:34 -0700 (PDT) Date: Sun, 23 May 2010 17:46:30 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Roman Bogorodskiy In-Reply-To: <20100523032720.GA89739@dirtyvegas> Message-ID: References: <20100518185201.GA2745@fsol> <20100523032720.GA89739@dirtyvegas> 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: Mon, 24 May 2010 03:46:35 -0000 On Sun, 23 May 2010, Roman Bogorodskiy wrote: > Jeff Roberson wrote: > >> 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. > > Tried today's -CURRENT and unfortunately the behaviour is still same. Can you give me a full stack trace? Do you have coredumps enabled? I would like to have you look at a few things in a core or send it to me with your kernel. Thanks, Jeff > > Roman Bogorodskiy >