bit of a noob question - please forgive

[stueyboy]

Hi guys

Used Amahi for a while but a bit of a virgin with greyhole and since I recently did a rebuild I though I would give it a try. I mistakenly left the root drive ticked and it has created the gh directory on there and has started to fill it up which I don't want for obvious reasons as my files are already physically in the shares anyway. My question is; if I uncheck the drive in the storage pool and let greyhole do it's thing overnight, will it move the files elsewhere? I have it set to create max copies but in reality only currently have one other physical disk to transfer into.

Thanks

[gboudreau]

If the files are in both your system drive, and on your secondary drive, then yes, you can just untick the system drive (/) and it will be fine.
But Greyhole will not remove the files from the /gh folder; you'll need to do it manually once you confirmed that all your files are on your other drive.

You can also force-remove the / partition from your storage pool, like this (as root):

Code: Select all

greyhole --going /gh

This will move single-copy files from /gh into your other drive, if you have any such files, and it will launch a fsck that will fix all the symlinks, so that your shared files all link to your second drive, and not to files in /gh anymore.
You will still need to un-check the / partition from the storage pool page once you executed that command.

Both approaches are equivalent (since you should not have any single-copy files), but the second one will get faster where you want to be.

[stueyboy]

Thanks for that. Incidentally, gh didn't copy all of my music folders when it first ran last night. Is this something to do with the sticky music setting? Seemed to only copy my itunes folder and I have about 5 other folders which are still only in my Music share.

One final thing. I have a NAS drive on my network and it would be good to add that to the pool. Is there a way to make that possible? Not sure if I can find a setting for that.

[gboudreau]

Sticky files only define the order in which drives are picked, when greyhole wants to move something in the pool.
For the Music Pool, the same drives will always be picked first, but if you selected to have a copy of your files on all drives (maximum extra copies), then this doesn't affect anything.

You can check if Greyhole is still working by looking at the /var/log/greyhole.log file:

Code: Select all

tail -f /var/log/greyhole.log

If it says 'Nothing to do... sleeping.' every 10 seconds, then it means it's idle. Otherwise, you should see a lot of log lines appear.
You'll need to wait for Greyhole to be idle before you can check if there's anything not right. Until then, it could have a lot of queued work still to do.
I'll implement a 'view queue' command in Greyhole soon, to allow users to see what's pending...

In theory, adding remote shares to the pool would be possible, but there's a bug somewhere in samba that makes it impossible at this time to do so. I reported the issue to the Samba team, but nobody acknowledge it, so I have very little hope that this will be fixed anytime soon, if ever.
At some point, I'll see if I can work around that issue in any way...

[gboudreau]

Next version of Greyhole will have this new "--view-queue" command:

Code: Select all

[gb@hda ~]$ greyhole --view-queue Greyhole Work Queue Statistics ============================== This table gives you the number of pending operations queued for the Greyhole daemon, per share. Write Delete Rename Backups 0 0 0 Books 0 0 0 CrashPlan 1 0 0 Games 0 0 0 gb 0 0 0 Music 0 0 0 Photos 0 0 0 RecordedTV 3 0 0 Software 0 0 0 Videos 1 0 0 VideosAttic 0 0 0 =========== Total 5 + 0 + 0 = 5