Bug #1249

panic: ffs_vfree: freeing free inode

Added by rumcic almost 6 years ago. Updated almost 2 years ago.

Status:FeedbackStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

As far as I know, it happened while another partition was being fsck-ed, but
other than that, there shouldn't have been much activity on the machine at the
time.

Unread portion of the kernel message buffer:
dev = #ad/0x20045, ino = 15, fs = /home
panic: ffs_vfree: freeing free inode
mp_lock = 00000000; cpuid = 0
Trace beginning at frame 0xdd0dd98c
panic(dd0dd9b0,c8520000,f1977000,c852012d,dd0dd9d8) at panic+0x14d
panic(c051a302,7,dd0dd9f4,0,0) at panic+0x14d
ffs_freefile(dd0ddae8,f,0,43ff) at ffs_freefile+0x186
handle_workitem_freefile(0,dd0ddce8,c5e4ab0c,dd0ddc8c,c02c5a67) at
handle_workitem_freefile+0x89
process_worklist_item(c5cfe400,49809881,c05a9ca0,0,c5be98c4) at
process_worklist_item+0x18c
softdep_process_worklist(0,c5cfe400,dd0ddd84,c02d5c86,0) at
softdep_process_worklist+0xa5
bio_ops_sync(0,49809881,c5cfe100,ff800000,c) at bio_ops_sync+0x2d
sched_sync(0,0,0,0,0) at sched_sync+0x16e
kthread_exit() at kthread_exit
boot() called on cpu#0
Uptime: 15m30s

dumping to dev #ad/0x20041, blockno 2107648
dump 3070 3069 3068 3067 3066 3065 3064 3063 3062 3061 3060 3059 3058 3057 3056
<snip>
4 3 2 1 0

GNU gdb 6.7.1
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-dragonfly".
(kgdb) bt
#0 dumpsys () at ./machine/thread.h:83
#1 0xc02874e9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:376
#2 0xc02877ae in panic (fmt=0xc051a302 "ffs_vfree: freeing free inode")
at /usr/src/sys/kern/kern_shutdown.c:801
#3 0xc03ced7b in ffs_freefile (pvp=0xdd0ddae8, ino=15, mode=17407)
at /usr/src/sys/vfs/ufs/ffs_alloc.c:1700
#4 0xc03d58b8 in handle_workitem_freefile (freefile=0xc5a63e20)
at /usr/src/sys/vfs/ufs/ffs_softdep.c:3044
#5 0xc03d4f88 in process_worklist_item (matchmnt=0x0, flags=<value optimized
out>) at /usr/src/sys/vfs/ufs/ffs_softdep.c:735
#6 0xc03d689f in softdep_process_worklist (matchmnt=0x0)
at /usr/src/sys/vfs/ufs/ffs_softdep.c:622
#7 0xc02d44f4 in bio_ops_sync (mp=0x0) at /usr/src/sys/kern/vfs_mount.c:1227
#8 0xc02d5c86 in sched_sync () at /usr/src/sys/kern/vfs_sync.c:243
#9 0xc027ac23 in suspend_kproc (td=Cannot access memory at address 0x8
) at /usr/src/sys/kern/kern_kthread.c:158
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--
Regards,
Rumko


Related issues

Related to Bug #1248: panic: ffs_vfree: freeing free inode Closed

History

#1 Updated by tuxillo almost 2 years ago

  • Description updated (diff)
  • Status changed from New to Feedback
  • Assignee deleted (0)

Venk,

Do you think this may still happen?

Cheers,
Antonio Huete

Also available in: Atom PDF