You mention "The way this is supposed to work is that if a brick is full
then *new* files will be created on other bricks with more space.". I am
not quite sure that this is the case when the new file is large enough
to fill up the space of the chosen brick, while it would fit on another.
On 28/01/2013 10:14 μμ, Jeff Darcy wrote:
On 01/28/2013 01:43 PM, Nux! wrote:
Thanks to "partner" on IRC who told me about this (quite big)
problem. Apparently in a distributed setup once a brick fills up
you start getting write failures. Is there a way to work around
this?
The way this is supposed to work is that if a brick is full then *new*
files will be created on other bricks with more space. However,
*existing* files are not relocated, so a write that requires allocating
new space for a file on a full brick will fail. There are three ways
that you can cause files to be relocated, freeing up space.
(1) A full rebalance via the CLI.
(2) Targeted rebalance of a directory using a special setxattr (see my
exchange with Dan Bretherton).
(3) Manual copying. When you create the new file it will be created on
the brick with the most space, then when you complete the copy the space
used by the original will be freed.
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
