On Thu, Feb 15, 2018 at 02:27:49AM +0500, mikhail wrote: > On Mon, 2018-02-12 at 09:56 +1100, Dave Chinner wrote: > > IOWs, this is not an XFS problem. It's exactly what I'd expect > > to see when you try to run a very IO intensive workload on a > > cheap SATA drive that can't keep up with what is being asked of > > it.... > > > > I am understand that XFS is not culprit here. But I am worried > about of interface freezing and various kernel messages with > traces which leads to XFS. This is my only clue, and I do not know > where to dig yet. I've already told you the problem: sustained storage subsystem overload. You can't "tune" you way around that. i.e. You need a faster disk subsystem to maintian the load you are putting on your system - either add more disks (e.g. RAID 0/5/6) or to move to SSDs. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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