Hello, Does this ring any bells with anyone? This issue still exists with FreeBSD 4.5-STABLE (4.6-PRERELEASE) and can be triggered on SMP machines e.g. by having several process attempting to create/rename/remove the same directory entry.
Cheers, -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] On Sat, Sep 22, 2001 at 04:31:38AM +0800, Yevgeniy Aleynikov wrote: > > > >Number: 30712 > >Category: kern > >Synopsis: fatal kernel trap during ufs_rename > >Confidential: no > >Severity: serious > >Priority: high > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Sep 21 13:30:01 PDT 2001 > >Closed-Date: > >Last-Modified: > >Originator: Yevgeniy Aleynikov > >Release: RELENG_4 > >Organization: > Infospace > >Environment: > FreeBSD myserver.mydomain.net 4.3-MYTAG FreeBSD 4.3-MYTAG #0: Thu Sep 20 01:24:53 >GMT 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/config i386 > >Description: > Currently two independed computers hit that problem. > Machine is stanard 1Xtreme boxes shipped by BSDi. DualP3, i440Gx, intel MB, onboard >adaptec SCSI, connected to winchester RAID box. > > Here what i've got: > gdb -k /kernel.debug vmcore.4 > GNU gdb 4.18 > SMP 2 cpus > IdlePTD 3039232 > initial pcb at 2666a0 > panicstr: ufs_rename: lost dir entry > panic messages: > --- > panic: ufs_rename: lost dir entry > mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 > boot() called on cpu#1 > > syncing disks... 16 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 > giving up on 1 buffers > Uptime: 16h20m39s > ... skipped... > >How-To-Repeat: > Not sure. > >Fix: > Couldnt figure out what's wrong. > >Release-Note: > >Audit-Trail: > >Unformatted: > >bt > #0 dumpsys () at ../../kern/kern_shutdown.c:473 > 473 ../../kern/kern_shutdown.c: No such file or directory. > (kgdb) bt > #0 dumpsys () at ../../kern/kern_shutdown.c:473 > #1 0xc015e9df in boot (howto=256) at ../../kern/kern_shutdown.c:313 > #2 0xc015ede0 in poweroff_wait (junk=0xc0233c84, howto=-535697984) > at ../../kern/kern_shutdown.c:581 > #3 0xc01c2239 in ufs_rename (ap=0xdf4fde60) at ../../ufs/ufs/ufs_vnops.c:1237 > #4 0xc01c363d in ufs_vnoperate (ap=0xdf4fde60) > at ../../ufs/ufs/ufs_vnops.c:2382 > #5 0xc019143b in rename (p=0xdf4c8740, uap=0xdf4fdf80) at vnode_if.h:645 > #6 0xc0205011 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 134590624, tf_esi = 135163912, tf_ebp = -1077937980, > tf_isp = -548413484, tf_ebx = 672122988, tf_edx = 134600160, tf_ecx = 0, > tf_eax = 128, tf_trapno = 22, tf_err = 2, tf_eip = 672621324, > tf_cs = 31, tf_eflags = 659, tf_esp = -1077938040, tf_ss = 47}) > at ../../i386/i386/trap.c:1155 > #7 0xc01f291b in Xint0x80_syscall () > #8 0x2807e125 in ?? () > #9 0x280e7f0c in ?? () > #10 0x8048e91 in ?? () > #11 0x8048d7d in ?? () > (kgdb) > > This is from 19 sep. snapshot kernel. I had exactly the same problem with Jul 10 >snapshot. > fsck didnt find anything wrong in filesystem. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-bugs" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
