Bug #1749

HAMMER fsstress panic in hammer_flush_inode_core 'ip->flush_state != HAMMER_FST_FLUSH'

Added by vsrinivas about 5 years ago. Updated 4 months ago.

Status:In ProgressStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:VFS subsystem
Target version:4.2.x

Description

Assertion 'ip->flush_state != HAMMER_FST_FLUSH' failed when running fsstress on
HAMMER on a very recent kernel; hammer_flush_inode_core called via
hammer_flush_inode, from hammer_vop_fsync, rooted at hammer_vfs_sync, from
sys_sync.

Core and vmimage at http://acm.jhu.edu/~me/kern.n4.gz and
http://acm.jhu.edu/~me/vmcore.n4.gz.

History

#1 Updated by tuxillo 4 months ago

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

Hi,

We really need to fsstress our filesystems out to see the results.

Cheers,
Antonio Huete

Also available in: Atom PDF