Problem adding 3rd HD

[bigfoot65]

Ensure ownership is your first administration user:users for /var/hda/files recursive.

[ Post made via Android ]

[jcostantino]

As it turns out, it wasn't a permissions problem - it was a bunch of symlinks that weren't visible on the client but I saw on the server. I moved the data out of the gh directory and merged it back into the share directory. Nothing had left the 2nd drive yet but I guess greyhole was doing something at some point and stopped.

So now I'm filling up the 2nd drive and will monitor it coming over to the 3rd drive and hopefully all is well.

[jcostantino]

Ok well now I'm still having an issue. Got a disk full error from drive 2 after copying to the smb share from another drive. Drives 2 and 3 are in the greyhole.conf and both are visible in the Storage Pool page and are selected.

Edit: Nevermind, I guess.... did a sudo greyhole -fo and now the log is going bonkers moving stuff from disk1 to disk2. I would have thought this would be dynamic.

[bigfoot65]

Yea, it takes time to get things moved. Usually the Greyhole fcsk runs nightly or at least mine does.

By forcing it, that will make things go quicker. Also how ever you configured your shares for copies will determine how drives fill up as well.

I am sure you know what your are doing, but just wanted to mention those things.

[jcostantino]

What is the best place to find an overview of how greyhole does its thing? I don't want a white paper on it, just an executive overview if you will. It seems like you copy a bunch of stuff and it fills up the first drive and either you copied less than the max capacity and it sorts it out overnight or you jammed the first drive full and it is out of space and the copy process fails. Is there a way to make it work like WHS's storage pooling? It seems as though bulk copying will become harder as the system fills up despite having enough space to copy.

Or am I missing something like distributing my shares on different drives of the pool?

[ Post made via Android ]

[bigfoot65]

The key is to keep the LZ (shares) separate from the GH drives. If you have the LZ and GH on the same drive, it is feasible that it could fill up.

A lot depends on how much data you are moving as well. There is a lot of good info in the wiki.
https://wiki.amahi.org/index.php/Greyhole
https://wiki.amahi.org/index.php/Greyhole_landing_zone
https://wiki.amahi.org/index.php/Storage_pooling

Hope this helps.

[jcostantino]

Ok so I should move /var/hda/files back to the boot drive... Somehow I figured I had to move the share volume off the first drive and on to the second. Can I do this in fstab without copying off everything? I changed the share path in the amahi control panel.

Can I move the files in the shares manually to another folder and then move the share location to the boot drive, then copy the files to the lz from the pool drive which will put them in the right place? I haven't copied too much stuff yet so I'm not bad off if I have to manually remove things and place them where they were out of the shares.

[ Post made via Android ]

[bigfoot65]

Yes change the mount in /etc/fstab top be drive# instead of /var/hda/files. That folder still exists on your OS drive unless you deleted it.

[jcostantino]

Ok it looks like I was unnecessarily complicating things. So it's install server, leave everything ALONE, format a drive, mount it, enable storage pool, watch magic happen.

The log shows the files being moved to the drives in a round-robin fashion which I guess is sort of "RAID-0 meets JBOD" and presumably I can mirror shares to as many drives as I have copies to create which is cool compared to WHS's method of two drives max.

[bigfoot65]

Yea, sometimes it's easier to start over. It sounds like its working correctly. I run my virtual and have not had any problems.