Bug #1913
panic: assertion: ip->flush_state != HAMMER_FST_FLUSH in hammer_flush_inode_core
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
I hit this assertion while running a loop of
/tmp/fsstress -n 6400 -p 1
on a fresh HAMMER v4 file system which was mounted normally.
Before the box crashed, I got 3 messages of the type:
HAMMER Warning: depth limit reached on setup recursion, inode ... ...
This box is running latest 2.9 and the file system was also created
after updating.
The core is in ~swildner/crash/crash31.tbz on leaf.
Regards,
Sascha