Balance Seems to Ignore Available Drive

[old-square-eyes]

I had 3 of my smaller drives fill up, and a 4th (much bigger) drive has plenty of space. This is obviously due to file copies settings. I added a new drive with the GUI and restarted the service. greyhole -s sees it.

I ran a FSCK for good measure and it found a bunch of files without the correct number of copies and copied them to the new drive. Great.

So I wanted to do a balance. I kicked that off, and reviewing the live logs I immediately started to see my new drive (with free space) being rejected. Here is an example...

DEBUG balance:   Drives with available space: /srv/dev-disk-by-uuid-qwerty-fd90-40fc-8c2c-786ac2754860/gh (1.52TB avail) - /srv/dev-disk-by-uuid-qwerty-d070-4452-ae8e-9e72df22a300/gh (249GB avail) - /srv/dev-disk-by-uuid-qwerty-3398-4b68-9b50-26f3c606e39c/gh (105GB avail) 
Jun 11 22:54:30 DEBUG balance:   Drives with enough free space, but no available space: /srv/dev-disk-by-uuid-qwerty-7b04-4f23-84ba-7aa3e857fb51/gh (-2.16GB avail) - /srv/dev-disk-by-uuid-qwerty-1d2a-4bfb-8f90-450c4fcc7323/gh (-8.87GB avail) - /srv/dev-disk-by-uuid-qwerty-12b5-4877-a232-88063e4ff2dc/gh (-9.39GB avail) 
Jun 11 22:54:30 DEBUG balance: ││││ Target drive: /srv/dev-disk-by-uuid-qwerty-d070-4452-ae8e-9e72df22a300/gh (249GB available)
Jun 11 22:54:30 DEBUG balance: ││├┘ Target drive needs more available space; moving a file there would do the opposite. Skipping.

This is happening over and over.