From owner-freebsd-current@FreeBSD.ORG Wed Oct 22 04:10:32 2003 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 F24D016A4B3 for ; Wed, 22 Oct 2003 04:10:31 -0700 (PDT) Received: from mail.ergobrains.co.jp (dns2.ergobrains.co.jp [61.204.41.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F0FF43FAF for ; Wed, 22 Oct 2003 04:10:30 -0700 (PDT) (envelope-from t-yonetani@ergobrains.co.jp) Received: from y0netan1 (d176.sys.p.ergobrains.co.jp [192.168.2.176]) by mail.ergobrains.co.jp (Postfix) with SMTP id DF3038B807; Wed, 22 Oct 2003 20:10:27 +0900 (JST) Date: Wed, 22 Oct 2003 20:10:27 +0900 From: YONETANI Tomokazu To: Oliver Fischer Message-ID: <20031022111027.GA63512@ergobrains.co.jp> References: <3F89ED52.9070204@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F89ED52.9070204@snafu.de> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org Subject: Re: panic: softdep_deallocate_dependencies: dangling deps 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: Wed, 22 Oct 2003 11:10:32 -0000 Hello. On 2003/10/13 02:09:54, Oliver Fischer wrote: > My notebook was a little bit "panic" this night. After rebooting I found > this message in my system log: > > panic: softdep_deallocate_dependencies: dangling deps I've been seeing this panic on NetFinity 6000R since end of September. -CURRENT is installed on a RAID partition, and the partition is controlled by ips driver, so it's possible that the root of my problem is completely different from yours, but anyway... To reproduce it, enable dump device and create many files in a directory: # mkdir foo; i=0; while :; do echo -n $i > foo/$i; i=$(($i + 1)); done and go to bed and you'll get a kernel dump in the crash dump directory in the next morning. At first I thought that the hard disk is damanged, but the following dd command doesn't panic the machine, just fills up the partition many times. # while :; do dd if=/dev/zero of=BIG bs=1048576; done With -CURRENT built from source as of D2003.10.21.00.00.00, I'm still able to reproduce this panic, together with new one: panic: handle_written_inodeblock: live inodedep Backtraces are available on request. -- YONETANI Tomokazu / Ergo-Brains Inc.