Amahi Forums

Hey all,

I'm not currently using Amahi (in the process of cleaning out my old WHS as we speak), but one of the things that irritated me about WHS that I'm hoping Amahi can help with is how WHS will automatically and periodically balance storage.

This causes me a couple of problems; Winamp will stop playing the music and µTorrent will say "the specified network path cannot be found".

I've googled and read these forums, and I know about the balancing command(s), but I'm really hoping there's a way to have balancing not be automatic. Alternatively, if any of you have any experience directly downloading to the storage pool / playing music off it while the files are shifted around and can confirm that the aforementioned problems don't exist, that'll be cool too.

I'll admit, I don't know the benefits of storage balancing, I only know of the disadvantages, so if I'm asking to turn off something hugely beneficial then feel free to correct me

Thanks in advance

PS: This isn't the only reason I'm switching, it's just the main annoyance I'm hoping to be rid of.

Thank you for that link, unfortunately I did not have more luck finding a specific answer to my question with the search results from that link than my original queries (I believe I used something akin to amahi + storage balancing when I made the Google searches I referenced in my original post).

In case I was unclear; I know that Greyhole can balance storage by using the -l or --balance parameters in the command line, what I was asking was whether Amahi has a cron job or daemon or something that automatically runs greyhole --balance or something to that effect.

Hopefully that makes it clearer, thanks again

I believe it does when the nightly fsck is done. I have seen it in my Greyhole logs.

I see... Do you know if there's a way to turn that off? I don't mind manually running that check every now and then.

Perhaps I should just set µTorrent to download to my local drive then move it to the server once it's been completed

Thanks

I think it's a cron job that runs it. Should be able to remove it.

Good stuff. Much appreciated