Date: Tue, 27 Nov 2001 15:00:57 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: freebsd-current@freebsd.org Subject: panic "handle_written_inodeblock: live inodedep" Message-ID: <20011127150056.B363@gsmx07.alcatel.com.au>
next in thread | raw e-mail | index | archive | help
Running -CURRENT from Sunday. Background: I had been building various
ports and then deleting the work directories. Some time later, I
unmounted that filesystem and ran fsck. The fsck reported about 190
files and 4 directories disconnected and reconnected them. Looking
through lost+found, I recognized most of the files as belonging to the
ports I had deleted. When I deleted the files, the system panic'd as
above (and then panic'd again trying to sync). The disk in question
probes as WDMA2. The backtrace from the crash dump is:
#0 dumpsys () at /3.0/cvs/src/sys/kern/kern_shutdown.c:492
#1 0xc01a289f in boot (howto=260) at /3.0/cvs/src/sys/kern/kern_shutdown.c:335
#2 0xc01a2cd9 in panic (fmt=0xc0298358 "bwrite: buffer is not busy???")
at /3.0/cvs/src/sys/kern/kern_shutdown.c:634
#3 0xc01d0bf3 in bwrite (bp=0xc32b5488) at /3.0/cvs/src/sys/kern/vfs_bio.c:670
#4 0xc01d117a in bawrite (bp=0xc32b5488)
at /3.0/cvs/src/sys/kern/vfs_bio.c:983
#5 0xc0181e4e in spec_fsync (ap=0xc79b1bac)
at /3.0/cvs/src/sys/fs/specfs/spec_vnops.c:409
#6 0xc0181961 in spec_vnoperate (ap=0xc79b1bac)
at /3.0/cvs/src/sys/fs/specfs/spec_vnops.c:119
#7 0xc0230ad5 in ffs_sync (mp=0xc0a98a00, waitfor=2, cred=0xc0730c00,
td=0xc0343844) at vnode_if.h:441
#8 0xc01dc865 in sync (td=0xc0343844, uap=0x0)
at /3.0/cvs/src/sys/kern/vfs_syscalls.c:657
#9 0xc01a2504 in boot (howto=256) at /3.0/cvs/src/sys/kern/kern_shutdown.c:244
#10 0xc01a2cd9 in panic (
fmt=0xc02a0fe0 "handle_written_inodeblock: live inodedep")
at /3.0/cvs/src/sys/kern/kern_shutdown.c:634
#11 0xc022cfb6 in handle_written_inodeblock (inodedep=0xc0f35500,
bp=0xc32ac0a8) at /3.0/cvs/src/sys/ufs/ffs/ffs_softdep.c:3798
#12 0xc022c892 in softdep_disk_write_complete (bp=0xc32ac0a8)
at /3.0/cvs/src/sys/ufs/ffs/ffs_softdep.c:3442
#13 0xc01d338d in bufdone (bp=0xc32ac0a8) at /3.0/cvs/src/sys/sys/buf.h:451
#14 0xc01d32c6 in bufdonebio (bp=0xc32ac0a8)
at /3.0/cvs/src/sys/kern/vfs_bio.c:2726
#15 0xc012eaf5 in ad_interrupt (request=0xc0deff40)
at /3.0/cvs/src/sys/sys/bio.h:107
#16 0xc0124fea in ata_intr (data=0xc0a3cc00)
at /3.0/cvs/src/sys/dev/ata/ata-all.c:588
#17 0xc0196c0e in ithread_loop (arg=0xc0a3cb80)
at /3.0/cvs/src/sys/kern/kern_intr.c:532
#18 0xc01961a5 in fork_exit (callout=0xc0196afc <ithread_loop>,
arg=0xc0a3cb80, frame=0xc79b1d48) at /3.0/cvs/src/sys/kern/kern_fork.c:786
The fsck after the panic again found lots of unconnected files, but
this time they could all be deleted successfully.
Has anyone else seen this?
Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011127150056.B363>