#1914 closed bug (fixed)
PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)!
| Reported by: | thorn | Owned by: | axeld |
|---|---|---|---|
| Priority: | critical | Milestone: | R1/alpha1 |
| Component: | System/Kernel | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | bga | |
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description (last modified by )
and again, hrev24348
bfs: Insert:1301: Name in use
Last message repeated 2 times.
wait interval 524536, scan pages 4356, free 2046, target 2050
wait interval 524304, scan pages 4358, free 2045, target 2051
wait interval 524072, scan pages 4360, free 2044, target 2052
wait interval 524072, scan pages 4360, free 2044, target 2052
bfs: Insert:1301: Name in use
PANIC: vnode 5:45465 already exists (node = 0x90c1b300, vnode->node = 0x91053d80)!
Welcome to Kernel Debugging Land...
Running on CPU 0
kdebug> bt
stack trace for thread 298 "svn"
kernel stack: 0x93af4000 to 0x93af8000
user stack: 0x7efe7000 to 0x7ffe7000
frame caller <image>:function + offset
93af797c (+ 52) 80082db3 <kernel>:invoke_debugger_command + 0x00cf
93af79b0 (+ 64) 80083b54 <kernel>:_ParseCommand__16ExpressionParserRi + 0x01f8
93af79f0 (+ 48) 80083546 <kernel>:EvaluateCommand__16ExpressionParserPCcRi + 0x01de
93af7a20 (+ 228) 80084c68 <kernel>:evaluate_debug_command + 0x0088
93af7b04 (+ 64) 80081986 <kernel>:kernel_debugger_loop__Fv + 0x017a
93af7b44 (+ 48) 800825d1 <kernel>:kernel_debugger + 0x010d
93af7b74 (+ 192) 800824b9 <kernel>:panic + 0x0029
93af7c34 (+ 64) 800486d6 <kernel>:new_vnode + 0x005a
93af7c74 (+ 64) 802d6d72 <bfs>:New__14InodeAllocatorP9block_runUiR9block_runPP5Inode + 0x014a
93af7cb4 (+ 176) 802dd3f1 <bfs>:Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x0571
93af7d64 (+ 96) 802e78eb <bfs>:bfs_create_dir__FPvT0PCciPx + 0x0107
93af7dc4 (+ 320) 8004ab0a <kernel>:dir_create__FiPcib + 0x0082
93af7f04 (+ 64) 8004ff78 <kernel>:_user_create_dir + 0x0094
93af7f44 (+ 100) 80092652 <kernel>:pre_syscall_debug_done + 0x0002 (nearest)
iframe at 0x93af7fa8 (end = 0x93af8000)
eax 0x50 ebx 0x458bc8 ecx 0x7ffe6734 edx 0xffff0104
esi 0x0 edi 0x19754e08 ebp 0x7ffe6760 esp 0x93af7fdc
eip 0xffff0104 eflags 0x206
vector: 0x63, error code: 0x0
93af7fa8 (+ 0) ffff0104
7ffe6760 (+ 48) 0032691f </boot/common/lib/libapr-1.so@0x00317000>:unknown + 0xf91f
7ffe6790 (+ 144) 002c8516 </boot/common/lib/libsvn_subr-1.so@0x002bb000>:unknown + 0xd516
7ffe6820 (+ 64) 002c861b </boot/common/lib/libsvn_subr-1.so@0x002bb000>:unknown + 0xd61b
7ffe6860 (+ 64) 0024fd35 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x1ad35
7ffe68a0 (+ 48) 0024d45f </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x1845f
7ffe68d0 (+ 176) 0024dd6d </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x18d6d
7ffe6980 (+ 64) 002b4bc5 </boot/common/lib/libsvn_delta-1.so@0x002b3000>:unknown + 0x1bc5
7ffe69c0 (+ 96) 00299f78 </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x7f78
7ffe6a20 (+ 112) 0029ab5a </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x8b5a
7ffe6a90 (+ 80) 00299126 </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x7126
7ffe6ae0 (+ 64) 00295466 </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x3466
7ffe6b20 (+ 176) 0023a1dc </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x51dc
7ffe6bd0 (+ 160) 00230426 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x18426
7ffe6c70 (+ 64) 002304f3 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x184f3
7ffe6cb0 (+ 80) 0020c9b1 </boot/common/bin/svn@0x00200000>:unknown + 0xc9b1
7ffe6d00 (+ 640) 002091fc </boot/common/bin/svn@0x00200000>:unknown + 0x91fc
7ffe6f80 (+ 44) 00204c45 </boot/common/bin/svn@0x00200000>:unknown + 0x4c45
7ffe6fac (+ 48) 001007ca 3453:runtime_loader_seg0ro@0x00100000 + 0x7ca
7ffe6fdc (+ 0) 7ffe6fec 3452:svn_main_stack@0x7efe7000 + 0xffffec
kdebug> vnode 0x90c1b300
VNODE: 0x90c1b300
device: -858993460
id: 0
ref_count: 78233
private_node: 0x00000000
mount: 0x3bbe0ad9
covered_by: 0x00000001
cache: 0xffffffff
flags: ---
advisory_lock: 0x00000000
kdebug>
kdebug> mount [1D [1Ds
address id root covers cookie fs_name
0x908ade00 1 0x908ade40 0x00000000 0x90861980 rootfs
0x908ade80 2 0x908adf00 0x908adec0 0x908619c0 devfs
0x908adf40 3 0x908adfc0 0x908adf80 0x908c4a50 pipefs
0x908e2540 4 0x908e2600 0x908e2580 0x908f1000 bfs
0x90b17880 5 0x90b17940 0x90b178c0 0x909d0c00 bfs
kdebug> mount 5
MOUNT: 0x90b17880
id: 5
device_name: /dev/disk/ata/0/slave/raw
fs_name: bfs
cookie: 0x909d0c00
root_vnode: 0x90b17940
covers_vnode: 0x90b178c0
partition: 0x908e9600
lock: 4807
flags:
kdebug>
Change History (19)
comment:1 by , 17 years ago
| Component: | File Systems/BFS → System/Kernel |
|---|---|
| Milestone: | R1 → R1/alpha1 |
| Priority: | normal → critical |
| Resolution: | → fixed |
| Status: | new → closed |
comment:2 by , 17 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Axel, kld again.
on Haiku hrev24635, vmware, 256M ram, 1st ata master 250M, 1st ata slave 2G, block size - 2K.
kdled on svn co svn://svn.berlios.de/haiku/buildtools/trunk buildtools
kdebug> message
vnode 5:553669 already exists (node = 0x9102c780, vnode->node = 0x91115480)!
kdebug> sc
stack trace for thread 197 "svn"
kernel stack: 0x9276a000 to 0x9276e000
user stack: 0x7efe7000 to 0x7ffe7000
frame caller <image>:function + offset
9276d97c (+ 52) 800843f3 <kernel>:invoke_debugger_command + 0x00cf
9276d9b0 (+ 64) 80085194 <kernel>:_ParseCommand__16ExpressionParserRi + 0x01f8
9276d9f0 (+ 48) 80084b86 <kernel>:EvaluateCommand__16ExpressionParserPCcRi + 0x01de
9276da20 (+ 228) 800862a8 <kernel>:evaluate_debug_command + 0x0088
9276db04 (+ 64) 80082f36 <kernel>:kernel_debugger_loop__Fv + 0x017a
9276db44 (+ 48) 80083be1 <kernel>:kernel_debugger + 0x010d
9276db74 (+ 192) 80083ac9 <kernel>:panic + 0x0029
9276dc34 (+ 64) 80049876 <kernel>:new_vnode + 0x005a
9276dc74 (+ 64) 8032be06 <bfs>:New__14InodeAllocatorP9block_runUiR9block_runPP5Inode + 0x014a
9276dcb4 (+ 176) 803324dd <bfs>:Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5Inode + 0x0571
9276dd64 (+ 96) 8033cccb <bfs>:bfs_create_dir__FPvT0PCciPx + 0x0107
9276ddc4 (+ 320) 8004bcc6 <kernel>:dir_create__FiPcib + 0x0082
9276df04 (+ 64) 800510d4 <kernel>:_user_create_dir + 0x0094
9276df44 (+ 100) 80094302 <kernel>:pre_syscall_debug_done + 0x0002 (nearest)
iframe at 0x9276dfa8 (end = 0x9276e000)
eax 0x55 ebx 0x45959c ecx 0x7ffe6644 edx 0xffff0104
esi 0x1b726960 edi 0x1b726960 ebp 0x7ffe6670 esp 0x9276dfdc
eip 0xffff0104 eflags 0x206
vector: 0x63, error code: 0x0
9276dfa8 (+ 0) ffff0104
7ffe6670 (+ 48) 0032691f </boot/common/lib/libapr-1.so@0x00317000>:unknown + 0xf91f
7ffe66a0 (+ 144) 002c8516 </boot/common/lib/libsvn_subr-1.so@0x002bb000>:unknown + 0xd516
7ffe6730 (+ 64) 002c864f </boot/common/lib/libsvn_subr-1.so@0x002bb000>:unknown + 0xd64f
7ffe6770 (+ 48) 0023b894 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x6894
7ffe67a0 (+ 64) 0023ba72 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x6a72
7ffe67e0 (+ 64) 0023bc46 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x6c46
7ffe6820 (+ 64) 0024d480 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x18480
7ffe6860 (+ 176) 0024dd6d </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x18d6d
7ffe6910 (+ 64) 002b4bc5 </boot/common/lib/libsvn_delta-1.so@0x002b3000>:unknown + 0x1bc5
7ffe6950 (+ 96) 00299f78 </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x7f78
7ffe69b0 (+ 112) 0029ab5a </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x8b5a
7ffe6a20 (+ 80) 00299126 </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x7126
7ffe6a70 (+ 64) 00295466 </boot/common/lib/libsvn_ra_svn-1.so@0x00292000>:unknown + 0x3466
7ffe6ab0 (+ 176) 0023a1dc </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x51dc
7ffe6b60 (+ 160) 00230426 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x18426
7ffe6c00 (+ 112) 0021f421 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x7421
7ffe6c70 (+ 64) 0021f544 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x7544
7ffe6cb0 (+ 80) 0020574e </boot/common/bin/svn@0x00200000>:unknown + 0x574e
7ffe6d00 (+ 640) 002091fc </boot/common/bin/svn@0x00200000>:unknown + 0x91fc
7ffe6f80 (+ 44) 00204c45 </boot/common/bin/svn@0x00200000>:unknown + 0x4c45
7ffe6fac (+ 48) 0010078e 1687:runtime_loader_seg0ro@0x00100000 + 0x78e
7ffe6fdc (+ 0) 7ffe6fec 1686:svn_main_stack@0x7efe7000 + 0xffffec
kdebug> cache -p
[*** READ/WRITE FAULT ***]
comment:3 by , 17 years ago
log before KDL
SCSI_DSK -- synchronize_cache: wait interval 943681, scan pages 968, free 4094, target 258 bfs: Insert:1306: Name in use Last message repeated 5 times. wait interval 973150, scan pages 730, free 4229, target 123 bfs: Insert:1306: Name in use Last message repeated 2 times. wait interval 984064, scan pages 641, free 4279, target 73 bfs: Insert:1306: Name in use Last message repeated 4 times. wait interval 986902, scan pages 618, free 4292, target 60 bfs: Insert:1306: Name in use PANIC: vnode 5:553669 already exists (node = 0x9102c780, vnode->node = 0x91115480)! Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 197 "svn"
comment:4 by , 17 years ago
Are you sure you've initialized your BFS volume, and are not using an older one from before the fix?
comment:6 by , 17 years ago
| Cc: | added |
|---|
This probably won't help much, but after you supposedly fixed this bug I never got this anymore. I do get the KDL on block notifier when checking out the tree tough.
follow-up: 8 comment:7 by , 17 years ago
I think I have similar situation with rev25276:
wait interval 927868, scan pages 1096, free 3785, target 311
bfs: Insert:1306: Name in use
Last message repeated 3 times.
wait interval 925085, scan pages 1118, free 3773, target 323
bfs: Insert:1306: Name in use
Last message repeated 2 times.
PANIC: vnode 3:545947 already exists (node = 0x90f91300, vnode->node = 0x90df4180)!
Welcome to Kernel Debugging Land...
Running on CPU 0
kdebug> bt
stack trace for thread 192 "svn"
kernel stack: 0x90a6c000 to 0x90a70000
user stack: 0x7efe7000 to 0x7ffe7000
frame caller <image>:function + offset
90a6f7fc (+ 52) 8008b2a3 <kernel>:invoke_debugger_command + 0x00cf
90a6f830 (+ 64) 8008c04c <kernel>:_ParseCommand__16ExpressionParserRi + 0x01f8
90a6f870 (+ 48) 8008ba3e <kernel>:EvaluateCommand__16ExpressionParserPCcRi + 0x01de
90a6f8a0 (+ 228) 8008d160 <kernel>:evaluate_debug_command + 0x0088
90a6f984 (+ 64) 80089dde <kernel>:kernel_debugger_loop__Fv + 0x017a
90a6f9c4 (+ 48) 8008aa91 <kernel>:kernel_debugger + 0x010d
90a6f9f4 (+ 192) 8008a979 <kernel>:panic + 0x0029
90a6fab4 (+ 64) 80051015 <kernel>:new_vnode + 0x0061
90a6faf4 (+ 80) 80588318 <bfs>:New__14InodeAllocatorP9block_runUiR9block_runP12fs_vnode_opsPP5Inode + 0x0170
90a6fb44 (+ 176) 8058eab9 <bfs>:Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5InodeP12fs_vnode_opsUl + 0x0579
90a6fbf4 (+ 96) 80597829 <bfs>:bfs_create__FP9fs_volumeP8fs_vnodePCciiPPvPx + 0x0125
90a6fc54 (+ 352) 800532ec <kernel>:create_vnode__FP5vnodePCciib + 0x0188
90a6fdb4 (+ 320) 80053682 <kernel>:file_create__FiPciib + 0x005a
90a6fef4 (+ 80) 80058994 <kernel>:_user_open + 0x00bc
90a6ff44 (+ 100) 8009b2a2 <kernel>:pre_syscall_debug_done + 0x0002 (nearest)
iframe at 0x90a6ffa8 (end = 0x90a70000)
eax 0x4f ebx 0x462c30 ecx 0x7ffe6374 edx 0xffff0104
esi 0x190ec0a0 edi 0x190ec1e0 ebp 0x7ffe63a0 esp 0x90a6ffdc
eip 0xffff0104 eflags 0x202
vector: 0x63, error code: 0x0
90a6ffa8 (+ 0) ffff0104
7ffe63a0 (+ 64) 003293be </boot/common/lib/libapr-1.so@0x00318000>:unknown + 0x113be
7ffe63e0 (+ 64) 002c7ff5 </boot/common/lib/libsvn_subr-1.so@0x002bb000>:unknown + 0xcff5
7ffe6420 (+ 80) 0023a918 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x5918
7ffe6470 (+ 64) 0024371a </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0xe71a
7ffe64b0 (+ 80) 00243c89 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0xec89
7ffe6500 (+ 64) 00244013 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0xf013
7ffe6540 (+ 64) 0023ba83 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x6a83
7ffe6580 (+ 64) 0023bc46 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x6c46
7ffe65c0 (+ 64) 0024d480 </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x18480
7ffe6600 (+ 176) 0024dd6d </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x18d6d
7ffe66b0 (+ 64) 002b4bc5 </boot/common/lib/libsvn_delta-1.so@0x002b3000>:unknown + 0x1bc5
7ffe66f0 (+ 96) 002a7b70 </boot/common/lib/libsvn_ra_dav-1.so@0x002a0000>:unknown + 0x7b70
7ffe6750 (+ 64) 00352430 </boot/common/lib/libneon.so@0x00343000>:unknown + 0xf430
7ffe6790 (+ 160) 002fb0d9 </boot/home/config/lib/libexpat.so@0x002f6000>:unknown + 0x50d9
7ffe6830 (+ 64) 002fa83a </boot/home/config/lib/libexpat.so@0x002f6000>:unknown + 0x483a
7ffe6870 (+ 48) 002fa02d </boot/home/config/lib/libexpat.so@0x002f6000>:unknown + 0x402d
7ffe68a0 (+ 64) 002f9f8f </boot/home/config/lib/libexpat.so@0x002f6000>:unknown + 0x3f8f
7ffe68e0 (+ 48) 0035284e </boot/common/lib/libneon.so@0x00343000>:unknown + 0xf84e
7ffe6910 (+ 48) 003527ff </boot/common/lib/libneon.so@0x00343000>:unknown + 0xf7ff
7ffe6940 (+ 48) 00351604 </boot/common/lib/libneon.so@0x00343000>:unknown + 0xe604
7ffe6970 (+ 48) 0034915e </boot/common/lib/libneon.so@0x00343000>:unknown + 0x615e
7ffe69a0 (+ 48) 00349c12 </boot/common/lib/libneon.so@0x00343000>:unknown + 0x6c12
7ffe69d0 (+ 112) 002add17 </boot/common/lib/libsvn_ra_dav-1.so@0x002a0000>:unknown + 0xdd17
7ffe6a40 (+ 112) 002adf57 </boot/common/lib/libsvn_ra_dav-1.so@0x002a0000>:unknown + 0xdf57
7ffe6ab0 (+ 112) 002a8f85 </boot/common/lib/libsvn_ra_dav-1.so@0x002a0000>:unknown + 0x8f85
7ffe6b20 (+ 176) 0023a1dc </boot/common/lib/libsvn_wc-1.so@0x00235000>:unknown + 0x51dc
7ffe6bd0 (+ 160) 00230426 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x18426
7ffe6c70 (+ 64) 002304f3 </boot/common/lib/libsvn_client-1.so@0x00218000>:unknown + 0x184f3
7ffe6cb0 (+ 80) 0020c9b1 </boot/common/bin/svn@0x00200000>:unknown + 0xc9b1
7ffe6d00 (+ 640) 002091fc </boot/common/bin/svn@0x00200000>:unknown + 0x91fc
7ffe6f80 (+ 44) 00204c45 </boot/common/bin/svn@0x00200000>:unknown + 0x4c45
7ffe6fac (+ 48) 0010078e 2798:runtime_loader_seg0ro@0x00100000 + 0x78e
7ffe6fdc (+ 0) 7ffe6fec 2797:svn_main_stack@0x7efe7000 + 0xffffec
comment:8 by , 17 years ago
Replying to kaliber:
I think I have similar situation with rev25276:
Sorry it was revision 25277 (using cutex in vm_cache)
comment:9 by , 17 years ago
Similar with a fresh built hrev25359 Installer was used to install Haiku on a smaller fresh empty disk (smaller than the boot disk), it produced errors but FinishScript was tried to be launched though. Bash complains it was not executable Then tried 'vi' on the FinishScript.
SCSI_DSK -- synchronize_cache:
wait interval 1000000, scan pages 512, free 4096, target 0
Last message repeated 3 times.
SCSI_DSK -- synchronize_cache:
bfs: invalid node [0x93945400] read from offset 89088 (block 3382), inode at 2114
bfs: BPlusTree::_SeekDown() could not open node 89088
bfs: Insert:1275: General system error
bfs: Update:288: General system error
bfs: Create:2468: General system error
bfs: invalid node [0x93945400] read from offset 89088 (block 3382), inode at 2114
bfs: BPlusTree::_SeekDown() could not open node 89088
bfs: Insert:1275: General system error
bfs: Update:288: General system error
bfs: Create:2468: General system error
PANIC: vnode 3:393737 already exists (node = 0x90c6b780, vnode->node = 0x90cdad80)!
Welcome to Kernel Debugging Land...
Running on CPU 0
kdebug> bt
stack trace for thread 245 "vim main()"
kernel stack: 0x92988000 to 0x9298c000
user stack: 0x70000000 to 0x70040000
frame caller <image>:function + offset
9298b7fc (+ 52) 800485db <kernel>:invoke_debugger_command + 0x00cf
9298b830 (+ 64) 80049384 <kernel>:_ParseCommand__16ExpressionParserRi + 0x01f8
9298b870 (+ 48) 80048d76 <kernel>:EvaluateCommand__16ExpressionParserPCcRi + 0x01de
9298b8a0 (+ 228) 8004a498 <kernel>:evaluate_debug_command + 0x0088
9298b984 (+ 64) 80047116 <kernel>:kernel_debugger_loop__Fv + 0x017a
9298b9c4 (+ 48) 80047dc9 <kernel>:kernel_debugger + 0x010d
9298b9f4 (+ 192) 80047cb1 <kernel>:panic + 0x0029
9298bab4 (+ 64) 8007611a <kernel>:new_vnode + 0x006a
9298baf4 (+ 80) 805c1338 <bfs>:New__14InodeAllocatorP9block_runUiR9block_runP12fs_vnode_opsPP5Inode + 0x0170
9298bb44 (+ 176) 805c7ad9 <bfs>:Create__5InodeR11TransactionP5InodePCcliUlPbPxPP5InodeP12fs_vnode_opsUl + 0x0579
9298bbf4 (+ 96) 805d0849 <bfs>:bfs_create__FP9fs_volumeP8fs_vnodePCciiPPvPx + 0x0125
9298bc54 (+ 352) 80078418 <kernel>:create_vnode__FP5vnodePCciib + 0x0188
9298bdb4 (+ 320) 800787b6 <kernel>:file_create__FiPciib + 0x005a
9298bef4 (+ 80) 8007db54 <kernel>:_user_open + 0x00bc
9298bf44 (+ 100) 8009f1c2 <kernel>:pre_syscall_debug_done + 0x0002 (nearest)
iframe at 0x9298bfa8 (end = 0x9298c000)
eax 0x55 ebx 0x62c584 ecx 0x7003f700 edx 0xffff0104
esi 0x18051537 edi 0x18047510 ebp 0x7003f72c esp 0x9298bfdc
eip 0xffff0104 eflags 0x202
vector: 0x63, error code: 0x0
9298bfa8 (+ 0) ffff0104
7003f72c (+1232) 00296153 <_APP_>:get_file_in_dir + 0x031b (nearest)
7003fbfc (+ 48) 00292589 <_APP_>:ml_open_file + 0x006d
7003fc2c (+ 48) 00292660 <_APP_>:check_need_swap + 0x0044
7003fc5c (+ 448) 002700ad <_APP_>:readfile + 0x0881
7003fe1c (+ 112) 0022656f <_APP_>:open_buffer + 0x0127
7003fe8c (+ 240) 00286b3f <_APP_>:main + 0x1acf
7003ff7c (+ 48) 00315fc5 <_APP_>:call_main__FPv + 0x0025
7003ffac (+ 48) 005a6f40 <libroot.so>:_get_next_team_info + 0x005c (nearest)
7003ffdc (+ 0) 7003ffec 2135:vim main()_245_stack@0x70000000 + 0x3ffec
comment:11 by , 16 years ago
I just noticed the KDL I get in bug #2590 is exactly the one reported here. Do you guys happen to have 2 mounted partitions with the same name? See the other bug for more information.
comment:12 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
This has likely been caused by the bug fixed in hrev28514. I'm closing this for now. Please reopen if you get it again with a checked partition.
comment:13 by , 15 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Sorry but I just got this with hrev32106. i could not get a stack trace because I have a USB keyboard but I got it 3 times in a row while trying to retrieve emails. After the third time I ran checkfs and got this:
[/boot/home]> checkfs /boot
print_server_settings (inode = 2099835), some blocks weren't allocated
TrackerSettings (inode = 2627462), some blocks weren't allocated
tracker_shelf (inode = 2627460), some blocks weren't allocated
multi_audio_settings (inode = 2627469), some blocks weren't allocated
new_mail_daemon (inode = 2692663), some blocks weren't allocated
checked 331188 nodes, 6 blocks not allocated, 0 blocks already set, 356 blocks could be freed
files 292866
directories 36824
attributes 946
attr. dirs 505
indices 47
Could be just luck but after this I was able to retrieve emails again without problems.
comment:14 by , 15 years ago
Wouldn't it be an idea to automatically execute a stack trace or a few other useful commands automatically after 30 seconds of inactivity in the kernel debugger? At least then usb people can report stack traces.
comment:15 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Since any kind of corruption could lead to this particular error, I would prefer to track this in #3150 only.
Also, if your block bitmap was messed up, it's no surprise that you ran into this error, and checkfs could fix it for you.
comment:16 by , 15 years ago
I guess I am missing something. You mean that #3150 is the same problem as this? because it does not look like it is.
comment:17 by , 15 years ago
As I said, any kind of corruption could lead to this panic. The outcome of any corruption can be very different.
comment:18 by , 15 years ago
So, what you are saying is that any error that could come from some kind of corruption should be posted on that bug instead of a new bug being opened? This will easily get confusing as people would not find that bug based on their own experience of a corruption unless what they see is a problem listing the contents of the directory.
Note I do not mind at all where the bugs are posted, it is just that that bug is, to anyone reading it, specifically about the kind of corruption that results in problems listing the contents of directories (which, BTW, I never saw again so it may even be fixed by some other of the changes you did).
comment:19 by , 15 years ago
That's basically what I'm saying. The point is, that every corruption can manifest itself through many different problems. It doesn't make any sense to open 10 different tickets about this, as long as it isn't clear it has a different cause.
While possible, I don't think all bugs leading to corruption have been fixed yet, and you cannot judge what the problems are from looking at the corruption, unfortunately.
Feel free to alter the description of #3150 if you want to. I would just continue to happily close related tickets as a duplicate of this one.
Note:
See TracTickets
for help on using tickets.
Fixed in hrev24607.