From owner-freebsd-current@FreeBSD.ORG Sun May 2 08:11:17 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75DF8106566B for ; Sun, 2 May 2010 08:11:17 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 544FD8FC14 for ; Sun, 2 May 2010 08:11:16 +0000 (UTC) Received: by pvb32 with SMTP id 32so238775pvb.13 for ; Sun, 02 May 2010 01:11:12 -0700 (PDT) Received: by 10.115.81.7 with SMTP id i7mr7180917wal.115.1272787872662; Sun, 02 May 2010 01:11:12 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id v13sm18153973wav.2.2010.05.02.01.11.11 (version=SSLv3 cipher=RC4-MD5); Sun, 02 May 2010 01:11:12 -0700 (PDT) Date: Sat, 1 May 2010 22:11:12 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Fabien Thomas In-Reply-To: <0018987E-06AE-40B1-9765-DC4641679601@netasq.com> Message-ID: References: <0018987E-06AE-40B1-9765-DC4641679601@netasq.com> 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: SUJ update 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: Sun, 02 May 2010 08:11:17 -0000 On Sun, 2 May 2010, Fabien Thomas wrote: > Hi Jeff, > > Before sending the 'bad' part i would like to say that it is very useful and save me a lot of time after a crash. > > I've updated the ports and there was no more space on the FS. > It end up with this backtrace (After one reboot the kernel crashed a second time with the same backtrace): When did you update? I fixed a bug that looked just like this a day or two ago. Thanks, Jeff > > (kgdb) bt > #0 doadump () at /usr/home/fabient/fabient-sandbox/sys/kern/kern_shutdown.c:245 > #1 0xc0a1a8fe in boot (howto=260) at /usr/home/fabient/fabient-sandbox/sys/kern/kern_shutdown.c:416 > #2 0xc0a1ad4c in panic (fmt=Could not find the frame base for "panic". > ) at /usr/home/fabient/fabient-sandbox/sys/kern/kern_shutdown.c:590 > #3 0xc0d058b3 in remove_from_journal (wk=0xc4b4aa80) at /usr/home/fabient/fabient-sandbox/sys/ufs/ffs/ffs_softdep.c:2204 > #4 0xc0d07ebb in cancel_jaddref (jaddref=0xc4b4aa80, inodedep=0xc46bed00, wkhd=0xc46bed5c) > at /usr/home/fabient/fabient-sandbox/sys/ufs/ffs/ffs_softdep.c:3336 > #5 0xc0d09401 in softdep_revert_mkdir (dp=0xc46ba6cc, ip=0xc4bba244) > at /usr/home/fabient/fabient-sandbox/sys/ufs/ffs/ffs_softdep.c:3898 > #6 0xc0d37c49 in ufs_mkdir (ap=0xc8510b2c) at /usr/home/fabient/fabient-sandbox/sys/ufs/ufs/ufs_vnops.c:1973 > #7 0xc0e7bc6e in VOP_MKDIR_APV (vop=0xc1085ea0, a=0xc8510b2c) at vnode_if.c:1534 > #8 0xc0add64a in VOP_MKDIR (dvp=0xc485e990, vpp=0xc8510bec, cnp=0xc8510c00, vap=0xc8510b6c) at vnode_if.h:665 > #9 0xc0add58f in kern_mkdirat (td=0xc4649720, fd=-100, path=0x804e9a0
, > segflg=UIO_USERSPACE, mode=448) at /usr/home/fabient/fabient-sandbox/sys/kern/vfs_syscalls.c:3783 > #10 0xc0add2fe in kern_mkdir (td=0xc4649720, path=0x804e9a0
, segflg=UIO_USERSPACE, mode=448) > at /usr/home/fabient/fabient-sandbox/sys/kern/vfs_syscalls.c:3727 > #11 0xc0add289 in mkdir (td=0xc4649720, uap=0x0) at /usr/home/fabient/fabient-sandbox/sys/kern/vfs_syscalls.c:3706 > #12 0xc0e5324b in syscall (frame=0xc8510d38) at /usr/home/fabient/fabient-sandbox/sys/i386/i386/trap.c:1116 > #13 0xc0e2b3c0 in Xint0x80_syscall () at /usr/home/fabient/fabient-sandbox/sys/i386/i386/exception.s:261 > #14 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) > > Regards, > Fabien > > >> Hello, >> >> I fixed a few SUJ bugs. If those of you who reported one of the following bugs could re-test I would greatly appreciate it. >> >> 1) panic on gnome start via softdep_cancel_link(). >> 2) Difficulty setting flags on /. This can only be done from a direct boot into single user but there were problems with tunefs that could lead to the kernel and disk becoming out of sync with filesystem state. >> 3) Kernel compiles without SOFTUPDATES defined in the config now work. >> >> I have had some reports of a hang waiting on journal space with certain types of activity. I have only had this reported twice and I am not able to reproduce no matter how much load I throw at the machine. If you reproduce this please try to get a coredump or minidump. >> >> Thanks, >> Jeff >> _______________________________________________ >> 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" >