Date: Tue, 16 Sep 2003 19:25:11 -0400 From: Ilya Krel <ilya@alchemistry.net> To: FreeBSD-gnats-submit@FreeBSD.org Subject: i386/56937: system panic during high network load Message-ID: <E19zPC3-0007ZN-00@alchemistry.net> Resent-Message-ID: <200309170010.h8H0AHZk000898@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 56937 >Category: i386 >Synopsis: system panic during high network load >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 16 17:10:16 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Ilya Krel >Release: FreeBSD 4.9-PRERELEASE i386 >Organization: >Environment: System: FreeBSD saruman.alchemistry.net 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #4: Mon Sep 15 23:07:33 EDT 2003 root@saruman.alchemistry.net:/usr/obj/usr/src/sys/ALCHEMISTRY i386 >Description: during dump of 10gb file to a samba share system paniced >How-To-Repeat: not tried to >Fix: Ive had some crashes after upgrade to 4.9, then the patch came out and i rebuilt everything. Its been over 2 weeks, and now system crashed again after writing about 10gb of data to non system disk: FreeBSD 4.9-PRERELEASE #3: Sat Aug 30 16:53:34 EDT 2003 Does above time mean there was no fix applied yet? This panic also caused a lot of files in lost+found. I am running softupdates,is there anything else i can do to prevent such data loss again? thx a lot gdb -k /var/crash/kernel.7 /var/crash/vmcore.7 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... IdlePTD at phsyical address 0x004a4000 initial pcb at physical address 0x003d1de0 panicstr: ffs_clusteralloc: map mismatch panic messages: --- panic: ffs_clusteralloc: map mismatch syncing disks... 37 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 giving up on 7 buffers Uptime: 16d3h18m12s dumping to dev #ad/0x20001, offset 901120 dump ata0: resetting devices .. done 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 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 0xc019ad82 in dumpsys () (kgdb) bt #0 0xc019ad82 in dumpsys () #1 0xc019ab53 in boot () #2 0xc019af91 in panic () #3 0xc028a70d in ffs_clusteralloc () #4 0xc0289ac3 in ffs_hashalloc () #5 0xc0289283 in ffs_reallocblks () #6 0xc01c60ca in cluster_write () #7 0xc02956f6 in ffs_write () #8 0xc01d0ea6 in vn_write () #9 0xc01aa825 in dofilewrite () #10 0xc01aa6de in write () #11 0xc030ec09 in syscall2 () #12 0xc02ff935 in Xint0x80_syscall () #13 0x809fe9b in ?? () #14 0x809ed92 in ?? () #15 0x80760e7 in ?? () #16 0x80762ad in ?? () #17 0x808949f in ?? () #18 0x80a5ff2 in ?? () #19 0x80a608e in ?? () #20 0x80a631e in ?? () #21 0x80a6ca3 in ?? () #22 0x806eaa4 in ?? () #23 0x806d159 in ?? () >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E19zPC3-0007ZN-00>