I'm seeing the equivalent[*] of xfs_extent_busy_flush() sleeping in my
beautiful io_submit() calls.
Questions:
- Is it correct that RWF_NOWAIT will not detect the condition that led
to the log being forced?
- If so, can it be fixed?
- Can I do something to reduce the odds of this occurring? larger
logs, more logs, flush more often, resurrect extinct species and
sacrifice them to the xfs gods?
- Can an xfs developer do something? For example, make it RWF_NOWAIT
friendly (if the answer to the first question was "correct")
[*] equivalent, because I'm actually looking at an older kernel that
lacks this function. But I'm moderately confident that the xfs_log_force
I'm seeing was transformed into xfs_extent_busy_flush by
ebf55872616c7d4754db5a318591a72a8d5e6896
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
