Re: ENOSPC with mkdir and rename

[Duncan <1i5t5.duncan@cox.net>]

Austin S Hemmelgarn posted on Mon, 04 Aug 2014 13:09:23 -0400 as
excerpted:

> Think of each chunk like a box, and each block as a block, and that you
> have two different types of block (data and metadata) and two different
> types of box (also data and metadata). The data boxes are four times the
> size of the metadata boxes, and they all have to fit in one really big
> container (the device itself).  You can only put data blocks in the data
> boxs, and you can only put metadata blocks in metadata boxes.  Say that
> in total, you can fit 128 data boxes in the large container, or you can
> replace one data box with up to four metadata boxes.  Even though you
> may only have a few blocks in a given box, the box still takes up the
> same amount of space in the larger container.  Thus, it's possible to
> have only a few blocks stored, but not be able to add any more boxes to
> the larger container.  A balance operation is essentially the equivalent
> of taking all of the blocks of a given type, and fitting them into the
> smallest number of boxes possible.

FWIW, that's a great analogy to stick up on the wiki somewhere, probably 
somewhere in the FAQ related to ENOSPC.  Please consider doing so.

(Someone took one of my explanations from the list and stuck it in the 
wiki, virtually word-for-word, with a link to the list post in the 
archives for more.  I was glad, as for some reason I just seem to work 
best on the lists, and seem to treat web pages as read-only, even if 
they're on a wiki I in theory have or can get write-privs on.  I'm 
suggesting someone, doesn't have to be you tho great if it is, do the 
same with this.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman