>>>>> On Sun,  2 Apr 2006 07:55:00 +0000 (UTC), juan@xtrarom.org said:

>> Number:         33179
>> Category:       kern
>> Synopsis:       LFS deadlock and another panic

> 	panic: lfs_truncate: negative bytes

We got similar panic as follows:

lfs_truncate: segment 919 short by 12288
panic: lfs_truncate: negative bytes
Stopped in pid 5.1 (ioflush) at netbsd:cpu_Debugger+0x5:        leave
db> bt 
cpu_Debugger() at netbsd:cpu_Debugger+0x5
panic() at netbsd:panic+0x1c8
lfs_update_seguse() at netbsd:lfs_update_seguse+0x1ac
lfs_truncate() at netbsd:lfs_truncate+0x951
ufs_inactive() at netbsd:ufs_inactive+0x310
lfs_inactive() at netbsd:lfs_inactive+0x4e
vrele() at netbsd:vrele+0x102
lfs_unmark_dirop() at netbsd:lfs_unmark_dirop+0x131
lfs_segwrite() at netbsd:lfs_segwrite+0x297
lfs_sync() at netbsd:lfs_sync+0x67
sync_fsync() at netbsd:sync_fsync+0x96
sched_sync() at netbsd:sched_sync+0x226

Environment:
System: NetBSD anoncvs1.netbsd.org 3.0_STABLE NetBSD 3.0_STABLE (ANONCVS) #11: Fri Mar 17 05:04:07 UTC 2006  root@:/usr/obj/sys/arch/amd64/compile.amd64/ANONCVS amd64
Architecture: x86_64
Machine: amd64

Since I forgot to specify RB_NOSYNC, crash dump isn't available.
(The machine just hung just after it started sync.)
--
soda