Why GlusterFS shows "no space left on device" error when one of many bricks becomes full?

Solution Verified - Updated -

Issue

  • GlusterFS volumes gives no space left on device errors when one of many bricks becomes full

  • The brick which is full continue to recieve file even with 10% default cluster.min-free-disk value.

  • Tuning Volume Options for cluster.min-free-disk value is not working.

Environment

  • Red Hat Storage Server 2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In