(Matt: I've cc'd you since you seem to have taken an interest in softupdates.
If you would prefer that I not cc you directly in the future, let me know and
it won't happen again.)
I'm posting to -hackers, since my last post of this type to stable didn't seem
to attract any attention.
It looks like I may have spoken too soon when I mentioned that I had no
problems with softupdates on my postfix based mail server. I have now had two
panics in the last month with a panicstr of
"softdep_lock: locking against myself". I thought that the first one might
have been a fluke until it repeated itself today.
Here's a transcript of the debugging session. I'm a novice at reading these,
so expert guidance is appreciated. (I've followed the example from the
handbook.)
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) exec-file kernel.1
(kgdb) core-file vmcore.1
IdlePTD 2617344
initial pcb at 219920
panicstr: softdep_lock: locking against myself
panic messages:
---
panic: softdep_fsync: pending ops
syncing disks... panic: softdep_lock: locking against myself
dumping to dev 20001, offset 4096
dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108
107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82
81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53
52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24
23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=260) at ../../kern/kern_shutdown.c:285
285 dumppcb.pcb_cr3 = rcr3();
(kgdb) where
#0 boot (howto=260) at ../../kern/kern_shutdown.c:285
#1 0xc0145e0c in at_shutdown (
function=0xc01f87ac <__set_sysuninit_set_sym_M_DIRREM_uninit_sys_uninit+4>,
arg=0xc0b18900, queue=-969667152) at ../../kern/kern_shutdown.c:446
#2 0xc019ef55 in acquire_lock (lk=0xc020ee84)
at ../../ufs/ffs/ffs_softdep.c:266
#3 0xc01a2909 in softdep_update_inodeblock (ip=0xc0b18900, bp=0xc34934b0,
waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3447
#4 0xc019dfdc in ffs_update (vp=0xc61ff700, waitfor=0)
at ../../ufs/ffs/ffs_inode.c:105
#5 0xc01a7436 in ffs_fsync (ap=0xc6340e68) at ../../ufs/ffs/ffs_vnops.c:258
#6 0xc01a580f in ffs_sync (mp=0xc0b06e00, waitfor=2, cred=0xc0752300,
p=0xc022d468) at vnode_if.h:499
#7 0xc016cb8b in sync (p=0xc022d468, uap=0x0) at ../../kern/vfs_syscalls.c:549
#8 0xc01459cd in boot (howto=256) at ../../kern/kern_shutdown.c:203
#9 0xc0145e0c in at_shutdown (
function=0xc01f9522 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2882>,
arg=0xc6641480, queue=0) at ../../kern/kern_shutdown.c:446
#10 0xc01a2baa in softdep_fsync (vp=0xc6641480)
at ../../ufs/ffs/ffs_softdep.c:3567
#11 0xc016f462 in fsync (p=0xc62a8760, uap=0xc6340f94)
at ../../kern/vfs_syscalls.c:2449
#12 0xc01d3a73 in syscall (frame={tf_es = 39, tf_ds = -1078001625,
tf_edi = -1077945532, tf_esi = 0, tf_ebp = -1077945772,
tf_isp = -969666588, tf_ebx = 134683656, tf_edx = 35, tf_ecx = 35,
tf_eax = 95, tf_trapno = 7, tf_err = 2, tf_eip = 671813520, tf_cs = 31,
tf_eflags = 582, tf_esp = -1077945788, tf_ss = 39})
at ../../i386/i386/trap.c:1100
#13 0xc01c9fac in Xint0x80_syscall ()
#14 0x804e9d0 in ?? ()
#15 0x8049f65 in ?? ()
#16 0x804be69 in ?? ()
#17 0x804bf7a in ?? ()
#18 0x8052ba9 in ?? ()
#19 0x804c6eb in ?? ()
#20 0x804a276 in ?? ()
#21 0x8049d65 in ?? ()
Other system information
------------------------
# uname -a
FreeBSD erouter0.it-datacntr.louisville.edu 3.3-STABLE FreeBSD 3.3-STABLE #1: Mon Sep
27 14:32:45 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/EROUTER i386
Softupdates are enabled on /var /and /var/log. (They are separate filesystems)
Drives are IDE.
/dev/wd2s1e 1016303 279793 655206 30% /var
/dev/wd0s1f 1016303 90322 844677 10% /var/log
Thanks for any guidance.
Regards,
--Keith Stevenson--
--
Keith Stevenson
System Programmer - Data Center Services - University of Louisville
[EMAIL PROTECTED]
PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
