Bug #2071
open
Panic on assertion: (int)(flg->seq - seq) > 0 in hammer_flusher_flush after inode error
0%
Description
ad10: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1500424384
ad10: FAILURE - WRITE_DMA48 status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND>
LBA=1500424384
HAMMER: Critical error inode=-1 error=5 while flushing meta-data
HAMMER: Forcing read-only mode
hammer: debug: forcing async flush ip 000000032433ccec
hammer: debug: forcing async flush ip 000000032433ccec
panic: assertion: (int)(flg->seq - seq) > 0 in hammer_flusher_flush
Trace beginning at frame 0xcbfadd10
panic(ffffffff,c07ace20,c064b39b,cbfadd40,cbfa00fc) at panic+0x101
panic(c064b39b,c067760e,c06353b6,0,cbfa0108) at panic+0x101
hammer_flusher_master_thread(cbfa0000,0,0,0,0) at hammer_flusher_master_thread+0x14e
lwkt_exit() at lwkt_exit
Uptime: 5d16h20m44s
Physical memory: 502 MB
Dumping 205 MB: 190 174 158 142 126 110 94 78 62 46 30 14
After an inode failure, HAMMER paniced on an assertion in hammer_flusher_flush.
ad10 was a WD EARS 1.5TB disk attached to a Silicon Image 3114 controller,
running via nata. The only I/O to the disk was a mirror-stream.
core and kernel are on leaf.dragonflybsd.org, /home/vsrinivas/hammerpanic.
Updated by vsrinivas over 13 years ago
Saw this panic again, with no disk errors present:
hammer: debug: forcing async flush ip 000000032b874602
panic: assertion: (int)(flg->seq - seq) > 0 in hammer_flusher_flush
Trace beginning at frame 0xcbf7fd10
panic(ffffffff,c07ace20,c064b39b,cbf7fd40,cbfa00fc) at panic+0x101
panic(c064b39b,c067760e,c06353b6,0,cbfa0108) at panic+0x101
hammer_flusher_master_thread(cbfa0000,0,0,0,0) at hammer_flusher_master_thread+0x14e
lwkt_exit() at lwkt_exit
Uptime: 23h2m13s
Physical memory: 502 MB
Dumping 193 MB: 178 162 146 130 114 98 82 66 50 34 18 2
Updated by swildner over 13 years ago
I had this panic too today on a 2.10 system.
Updated by swildner over 13 years ago
Backtrace is slightly different though:
#4 0xc01be6a3 in panic (fmt=0xc03c0534 "assertion: %s in %s") at /home/s/
projects/dailybuild/src/sys/kern/kern_shutdown.c:833
#5 0xc02eed92 in hammer_flusher_flush (arg=0xce840000) at /home/s/projects/
dailybuild/src/sys/vfs/hammer/hammer_flusher.c:352
#6 hammer_flusher_master_thread (arg=0xce840000) at /home/s/projects/
dailybuild/src/sys/vfs/hammer/hammer_flusher.c:269
#7 0xc01c741b in lwkt_deschedule_self (td=Cannot access memory at address 0x8)
at /home/s/projects/dailybuild/src/sys/kern/lwkt_thread.c:283
Updated by swildner over 13 years ago
I should mention that the system I'm seeing this on is NATA too, just like
Venkatesh's.