[DragonFlyBSD - Bug #1749] (In Progress) HAMMER fsstress panic in hammer_flush_inode_core 'ip->flush_state != HAMMER_FST_FLUSH'

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Mon Jan 19 05:25:24 PST 2015


Issue #1749 has been updated by tuxillo.

Description updated
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

----------------------------------------
Bug #1749: HAMMER fsstress panic in hammer_flush_inode_core 'ip->flush_state != HAMMER_FST_FLUSH'
http://bugs.dragonflybsd.org/issues/1749#change-12525

* Author: vsrinivas
* Status: In Progress
* Priority: Normal
* Assignee: 
* Category: VFS subsystem
* Target version: 4.2.x
----------------------------------------
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.



-- 
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



More information about the Bugs mailing list