From owner-freebsd-current@FreeBSD.ORG Sun May 2 07:10:09 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 C38D5106566C for ; Sun, 2 May 2010 07:10:09 +0000 (UTC) (envelope-from fabien.thomas@netasq.com) Received: from work.netasq.com (gateway.netasq.com [91.212.116.2]) by mx1.freebsd.org (Postfix) with ESMTP id 653888FC15 for ; Sun, 2 May 2010 07:10:09 +0000 (UTC) Received: from [192.168.0.1] (unknown [10.0.0.126]) by work.netasq.com (Postfix) with ESMTPSA id 8FBBF740001; Sun, 2 May 2010 09:10:00 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Fabien Thomas In-Reply-To: Date: Sun, 2 May 2010 09:10:07 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <0018987E-06AE-40B1-9765-DC4641679601@netasq.com> References: To: Jeff Roberson X-Mailer: Apple Mail (2.1078) 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 07:10:09 -0000 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): (kgdb) bt #0 doadump () at = /usr/home/fabient/fabient-sandbox/sys/kern/kern_shutdown.c:245 #1 0xc0a1a8fe in boot (howto=3D260) at = /usr/home/fabient/fabient-sandbox/sys/kern/kern_shutdown.c:416 #2 0xc0a1ad4c in panic (fmt=3DCould 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=3D0xc4b4aa80) at = /usr/home/fabient/fabient-sandbox/sys/ufs/ffs/ffs_softdep.c:2204 #4 0xc0d07ebb in cancel_jaddref (jaddref=3D0xc4b4aa80, = inodedep=3D0xc46bed00, wkhd=3D0xc46bed5c) at /usr/home/fabient/fabient-sandbox/sys/ufs/ffs/ffs_softdep.c:3336 #5 0xc0d09401 in softdep_revert_mkdir (dp=3D0xc46ba6cc, ip=3D0xc4bba244) at /usr/home/fabient/fabient-sandbox/sys/ufs/ffs/ffs_softdep.c:3898 #6 0xc0d37c49 in ufs_mkdir (ap=3D0xc8510b2c) at = /usr/home/fabient/fabient-sandbox/sys/ufs/ufs/ufs_vnops.c:1973 #7 0xc0e7bc6e in VOP_MKDIR_APV (vop=3D0xc1085ea0, a=3D0xc8510b2c) at = vnode_if.c:1534 #8 0xc0add64a in VOP_MKDIR (dvp=3D0xc485e990, vpp=3D0xc8510bec, = cnp=3D0xc8510c00, vap=3D0xc8510b6c) at vnode_if.h:665 #9 0xc0add58f in kern_mkdirat (td=3D0xc4649720, fd=3D-100, = path=3D0x804e9a0
,=20 segflg=3DUIO_USERSPACE, mode=3D448) at = /usr/home/fabient/fabient-sandbox/sys/kern/vfs_syscalls.c:3783 #10 0xc0add2fe in kern_mkdir (td=3D0xc4649720, path=3D0x804e9a0
, segflg=3DUIO_USERSPACE, mode=3D448) at /usr/home/fabient/fabient-sandbox/sys/kern/vfs_syscalls.c:3727 #11 0xc0add289 in mkdir (td=3D0xc4649720, uap=3D0x0) at = /usr/home/fabient/fabient-sandbox/sys/kern/vfs_syscalls.c:3706 #12 0xc0e5324b in syscall (frame=3D0xc8510d38) 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)=20 Regards, Fabien > Hello, >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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"