Moving Files among hard disks

[gastone]

I have installed just this week my amahi server and after browsing through the forum and the wiki i decided that mounting my shares locally to transfer my files is the best way so the files will go straight to the pool and not through the root disk.
So i mounted my ntfs disks too and started transfering. In the begining everything worked well. yesterday i added another share through the amahi dashboard and restarted the mount_shares_locally in order for the new share to appear too. Everything was ok, the new folder appeared in nmt\samba\ but ever since instead of straight to the pool everything passes through the root disk. And even the files transfered over the network do the same.... I check on the dashboard and i see the root disk filling up and emptying....
What has gone wrong????
I have done the conversion to mySQL.

Thanks

[gboudreau]

The copying files into your shares, they always get copied into what Greyhole calls the 'landing zone'.
The LZ is the path you have defined as the 'Location' of your shares (see the Amahi Dashboard, Setup > Shares page).
By default, that means all incoming files will end up on /var/hda/files/share_name
The files are only there temporarily. They will get moved into the drives part of your storage pool as soon as possible, by the Greyhole daemon, that runs in background.
That means that copying files into your shares fast enough, you could fill your / partition, since Greyhole would sometimes be slower to move the files away from the LZ.
You can change the Location of your shares to any other drive if you'd like (/var/hda/files/drives/drive1/share_name for example). Just run greyhole --fsck after you did, to have your files re-appear in your share. Alternatively, you could move all the symlinks from the old LZ dirs to the new ones. Something like: mv /var/hda/files/something/* /var/hda/files/drives/drive1/something/, and repeat for each share. This would fix your shares after you move the LZ, without needing a fsck. But I'd still run a fsck anyway after all this, just to be sure.

[gastone]

Thanks for your answer!
Now that i copied everything I don't think that it will bother me any more...
I added a 3rd 2TB disk and i though that the greyhole would balance the data among disks but it didn't. The 2 old disks are still 90% full and the new one is empty. Two days now nothing changed.
Is that normal?

[gboudreau]

Yes. GH does not balance old files, only new files.
You can ask it to balance everything with this command:

Code: Select all

greyhole --balance

[gastone]

Thanks again!!!
Just what i needed!!!
I came across in some post a command that transfers the files from the LZ to the pool without having to wait for midnight. Would you happen to know it too???

[NeverSimple]

I came across in some post a command that transfers the files from the LZ to the pool without having to wait for midnight. Would you happen to know it too???

I'm pretty sure he does... But here are all options for greyhole (you can get this by entering just 'greyhole' in a terminal):

Code: Select all

Usage: greyhole [ACTION] [OPTIONS] Where ACTION is one of: -?, --help Display this help and exit. -D, --daemon Start the daemon. -f, --fsck Schedule a fsck. -l, --balance Balance available space on storage pool devices. -s, --stats Display storage pool statistics. -q, --view-queue Display the current work queue. -a, --empty-attic Empty the attic. -b, --debug=filename Debug past file operations. -p, --prerotate Pre-rotate task (for logrotate). -P, --postrotate Post-rotate task (for logrotate). -t, --thaw[=path] Thaw a frozen directory. Greyhole will start working on files inside <path>. If you don't supply an option, the list of frozen directories will be displayed. -w, --wait-for[=path] Tell Greyhole that the missing drive at <path> will return soon, and that it shouldn't re-create additional file copies to replace it. If you don't supply an option, the available options (paths) will be displayed. -g, --gone[=path] Tell Greyhole that the missing drive at <path> is gone for good. Greyhole will start replacing the missing file copies instantly. If you don't supply an option, the available options (paths) will be displayed. -n, --going[=path] Tell Greyhole that you want to remove a drive. Greyhole will then make sure you don't loose any files, and that the correct number of file copies are created to replace the missing drive. If you don't supply an option, the available options (paths) will be displayed. For --fsck, the available OPTIONS are: -e, --email-report Send an email when fsck completes, to report on what was checked, and any error that was found. -y, --dont-walk-graveyard Speed up fsck by skipping the scan of the graveyard directories. Scanning the graveyards is only required to re-create symbolic links that might be missing from your shared directories. -d, --dir=path Only scan a specific directory, and all sub-directories. The specified directory should be a Samba share, or a sub-directory of a Samba share.

The option you're looking for is --fsck

HTH,

Richard

[gastone]

Thank you very much!!!
It will take me some time but I'm sure I'll manage to get the hang of it...