Bug #1717

HAMMER panic in hammer_cursor_down()

Added by josepht1 about 5 years ago. Updated 6 months ago.

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

0%

Category:VFS subsystem
Target version:4.2.x

Description

I got the following panic (sorry it's just a backtrace):

panic: BTYPE MISMATCH L
Trace beginning at frame 0xdf17171c
panic(df171740,cee83300,df1717f4,e3903248,df171764) at panic+0x8c
panic(c06029f3,4c,0,e3903248,cefdf000) at panic+0x8c
hammer_cursor_down(df1717f4) at hammer_cursor_down+0x113
hammer_btree_iterate_reverse(df1717f4,df171a58,0,0,cefdf040) at
hammer_btree_iterate_reverse+0x1c0
hammer_ioc_prune(df171a58,d91c5610,dc874f00,df17195c,1) at
hammer_ioc_prune+0x682
hammer_ioctl(d91c5610,c0fc6801,dc874f00,1,d50b1050) at
hammer_ioctl+0x1c8
hammer_vop_ioctl(df171ac8,df171abc,d8797ab4,d8797ab4,d8cf32f0) at
hammer_vop_ioctl+0x2f
vop_ioctl(d8cead10,c47f3d28,c0fc6801,dc874f00,1) at vop_ioctl+0x58
vn_ioctl(d50f0338,c0fc6801,dc874f00,d50b1050,df171cf0) at
vn_ioctl+0xe0
mapped_ioctl(5,c0fc6801,280f0188,0,df171cf0) at mapped_ioctl+0x3e4
sys_ioctl(df171cf0,6,0,0,d86fa9d0) at sys_ioctl+0x17
syscall2(df171d40) at syscall2+0x20e
Xint0x80_syscall() at Xint0x80_syscall+0x36

I've uploaded the kern.25.gz and vmcore.25.gz to my leaf account.

Thanks,
Joe

History

#1 Updated by tuxillo 6 months ago

  • Description updated (diff)
  • Category set to VFS subsystem
  • Status changed from New to Feedback
  • Assignee deleted (0)
  • Target version set to 4.2.x

Hi Josepht,

It seems that it happened while pruning the fileystem.
Is there any way to reproduce this one? It seems weird to me that this would still be relevant and that none has reported it again.

Cheers,
Antonio Huete

Also available in: Atom PDF