Issue #2647 has been reported by tuxillo.
----------------------------------------
Bug #2647: HAMMER panic on 3.6.0
http://bugs.dragonflybsd.org/issues/2647
* Author: tuxillo
* Status: New
* Priority: Normal
* Assignee:
* Category: VFS subsystem
* Target version: 3.8.0
----------------------------------------
Hi,
I've had the following panic on my NAS after checking out our tree and directly
starting a build:
No dump is available.
panic: hammer_sync_record_callback: illegal add during inode deletion record
0xffffffe0d21199070
cpuid = 0
Trace beginning at frame 0xffffffe0cdd47770
panic at panic+0x223 0xffffffff80561c0c
panic at panic+0x223 0xffffffff80561c0c
hammer_sync_record_callback() at hammer_sync_record_callback+0x11f
0xffffffff8075f278
hammer_rec_rb_tree_RB_SCAN() at hammer_rec_rb_tree_RB_SCAN+0xf9
0xffffffff8076a755
hammer_sync_inode() at hammer_sync_inode+0x282 0xffffffff80761ffb
hammer_flusher_flush_inode() at hammer_flusher_flush_inode+0x62
0xffffffff8075e50c
hammer_fls_rb_tree_RB_SCAN() at hammer_fls_rb_tree_RB_SCAN+0x100
0xffffffff8075d1f4
hammer_flusher_slave_thread() at hammer_flusher_slave_thread+0x7a
0xffffffff8075d2e3
Debugger("panic")
CPU0 stopping CPUs: 0x00000002
stopped
Stopped at Debugger+0x38: movb $0,0x8945f2(%rip)
db>
The following comment enclose the if where the panic is hit.
* XXX There may be a case with RECORD_ADD with DELETED_FE set
* that we currently panic on.
Not sure if that's relevant.
Cheers,
Antonio Huete
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://bugs.dragonflybsd.org/my/account
