Project

General

Profile

Actions
Copy link

Bug #1749

open

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

Added by vsrinivas over 14 years ago. Updated over 3 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
VFS subsystem
Target version:
6.4
Start date:
Due date:
% Done:

0%

Estimated time:

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.

Actions
Copy link
 #1

Updated by tuxillo almost 10 years 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

Hi,

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

Cheers,
Antonio Huete

Actions
Copy link
 #2

Updated by tuxillo over 3 years ago

  • Target version changed from 4.2 to 6.0
Actions
Copy link

Also available in: Atom PDF