First HDD filling up even with pool

[GlobalOne]

Hi everyone,

I am having some strange problems with my storage pool. As it stands right now, I have a small HDD that has just the root partition, and is not included in the storage pool configuration. I then have another one slightly larger as well as a 1TB, where both of those are in the storage pool. I then created a new share that is also configured to use the storage pool. Next, I'm running the script that mounts all shares locally, so that CrashPlan Backup can use the locally mounted share (instead of just going to the directory where the share puts its files). Therefore, all backups made by CrashPlan should be dealt with by Gereyhole and spread out to the pool.

However, there are two problems I am having with this. First, it's not working. All the data is all on one hard drive, and isn't wanting to move. I tried it once before and it worked, but now suddenly not anymore. Second, while it was still working, I noticed that it dumped all the files that were being sent to the share on the system hard drive, where from there it would eventually spread out. That drive is very small though, and quickly fills up. Is there a way to change this?\

Thanks for your help!

[gboudreau]

To change where the file first lands, before getting moved to the pool, you need to change the location of the shares, from the default /var/hda/files/share_name to somewhere else.
For example, you can create a directory /var/hda/files/drives/drive2/share_name/ and use that (in the amahi dashboard, Setup > Shares page).

To see why files wouldn't be moving: http://forums.amahi.org/viewtopic.php?f=39&t=1989

[VirtualMe]

If the landing zone for a share is changed to a drive that is part of the storage pool, when Greyhole distributes the file will it just make a symlink on that drive instead of physically moving the file to a different directory on that drive?

[gboudreau]

It won't just make a symlink. At the moment, I think it will rsync the file at the right location, even if that location is on the same drive.
I already have an improvement issue filed to use rename instead of rsync for such.

*edit: Greyhole 0.8.4 and up will include this improvement. It's been committed already.