Why GlusterFS shows "no space left on device" error when one of many bricks becomes full?
Issue
-
GlusterFS volumes gives
no space left on deviceerrors when one of many bricks becomes full -
The brick which is full continue to recieve file even with 10% default
cluster.min-free-diskvalue. -
Tuning Volume Options for
cluster.min-free-diskvalue is not working.
Environment
- Red Hat Storage Server 2.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
