From owner-freebsd-current@FreeBSD.ORG Mon Mar 29 19:31:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABC0816A4CE for ; Mon, 29 Mar 2004 19:31:28 -0800 (PST) Received: from sherryl.salk.edu (sherryl.snl.salk.edu [198.202.70.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7929043D1D for ; Mon, 29 Mar 2004 19:31:28 -0800 (PST) (envelope-from jorge@salk.edu) Received: from merckx.snl.salk.edu (merckx.snl.salk.edu [198.202.70.90]) by sherryl.salk.edu (8.12.10/8.12.10) with ESMTP id i2U3VK81070008; Mon, 29 Mar 2004 19:31:21 -0800 (PST) Date: Mon, 29 Mar 2004 19:31:16 -0800 (PST) From: Jorge Aldana X-X-Sender: jorge@merckx.snl.salk.edu To: DrumFire In-Reply-To: <000d01c415af$bad6dcc0$aaa27450@softec> Message-ID: <20040329191539.Q17011@merckx.snl.salk.edu> References: <000d01c415af$bad6dcc0$aaa27450@softec> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "freebsd-current@freebsd.org" Subject: Re: Filesystem panic in 5.2.1-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Tue, 30 Mar 2004 03:31:28 -0000 I also have had similar problems but usually manually fsck /usr (also right after the crash), then on building more ports I will get another reboot. The only thing I'm doing is adding ports, no other user action or gui just ports. I've only gotten it to crash during the bigger ports (openoffice, jdk) and makes me point or wonder about softupdate or filesystem problems (I now have directory's which are not deleteble, renamed to be able to continue). What other info can I provide to help with this, logs are have no extra info, even when booting up with the extra logging enabled. Also I have hint.acpi.0.disabled="1" in my /boot/loader.conf, should I turn it on? Jorge On Mon, 29 Mar 2004, DrumFire wrote: > >I'll see if that makes anything more stable, but otherwise I'd be > >interested in other people's comments about the crashes I've seen. > > I've a kernel panic on ffs_copyonwrite on a 5.2.1 FreeBSD Box, If i > try to access to filesystem, while fsck in background try to mark it > clean. > > For a blackout, my /dev/ad0s1d on /usr gone broken. When I rebooted, > after login, in ps I've seen that was a fsck in background. Then > i tried to install ports with sysinstall while fsck cleening the > filesystem, and after 4-5 minutes kernel gone in panic. > > I've put background_fsck="NO" in /etc/rc.conf so when filesystem is > broken, I'll check and clean it before login. > > If needed I can reproduce the problem and post here dmesg etc. > > Bye. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >