System Crash - please help me figure it out...

[bsd at perimeter.co.za]

Dear Hackers, 

I have experienced a system crash for the first time in 10 months (last year 
in august I had a vinum issue which has been resolved with your help). 

Fortunately I still have a kernel with debugging enabled running, and the 
gdbmods script, so I can submit some useful data with this email. 

First, here is an extract from /var/log/messages:
========
Jun  9 10:59:37 obelix /kernel: /peri: bad dir ino 427318 at offset 384: 
mangled entry
Jun  9 10:59:37 obelix /kernel: panic: ufs_dirbad: bad dir
Jun  9 10:59:37 obelix /kernel:
Jun  9 10:59:37 obelix /kernel: syncing disks... 21 1 1 1 1 1 1 1 1 1 1 1 1 
1 1 1 1 1 1
Jun  9 10:59:37 obelix /kernel: 1 1
Jun  9 10:59:37 obelix /kernel: done
Jun  9 10:59:37 obelix /kernel: Uptime: 2d21h35m21s
Jun  9 10:59:37 obelix /kernel:
Jun  9 10:59:37 obelix /kernel: dumping to dev #ad/0x20001, offset 1638560
Jun  9 10:59:37 obelix /kernel: dump ata0: resetting devices .. done
Jun  9 10:59:37 obelix /kernel: 223 222 221 220 219 218 217 216 215 214 213 
212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 19
6 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 
177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161
160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 
141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 12
5 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 8
6 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 Copyright (c) 1992-2003 The FreeBS
D Project.
Jun  9 10:59:37 obelix /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 
1989, 1991, 1992, 1993, 1994
Jun  9 10:59:37 obelix /kernel: The Regents of the University of California. 
All rights reserved.
Jun  9 10:59:37 obelix /kernel: FreeBSD 4.8-RELEASE #14: Tue Jun  3 14:48:15 
SAST 2003
Jun  9 10:59:37 obelix /kernel: 
peri at obelix.perimeter.co.za:/usr/obj/usr/src/sys/obelix
======== 

 From this it seems that there was an inode problem on /peri ?!?  FYI, here 
is df:
========
root obelix:~# df
Filesystem     1K-blocks    Used    Avail Capacity  Mounted on
/dev/ad0s1a      1032142   82206   867366     9%    /
/dev/ad0s1e     17634326 3632512 12591068    22%    /usr
/dev/vinum/vm1  38787345 4981936 30702422    14%    /peri
procfs                 4       4        0   100%    /proc
root obelix:~#
======== 

As you can see the /peri 'disk' is a vinum device. 

I expected that I might have the same problem as before, but this is what 
gdmods gives me: 

(see http://docs.perimeter.co.za/crash/2003-06/20030609_1448_a ) 

 From this it appears that the fault does not occur within vinum code at all. 

I am no hacker myself, so if you would like me to type more useful commands 
at the gdb prompt please mail me and I'll follow your instructions. 

Regards,
Patrick O'Reilly.