Is there a way to prevent write-back cache starvation caused by a process that monopolizes the cache?

Solution Verified - Updated -

Issue

There should be a possibility of limiting use of a cache on per-device basis, otherwise there is a possibility for a slow device (for example, a sluggish NFS client) to take all or the most of the write-back cache. There should be a limitation for particular device to use not more than the given percentage of the write-back cache. This is useful in situations where we want to avoid one device taking all or most of the write-back cache, for example in case of an NFS mount that is prone to get stuck, or a FUSE mount which cannot be trusted to play fair.

Environment

  • Red Hat Enterprise Linux 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.