However, unfortunately it doesn't seem to work on my Amahi installation.
When I access the app at "http://gh-du.home.com/" I receive the following error message:
Error: /usr/share/greyhole/gh-disk-usage.log file not found.
You need to run 'greyhole --fsck --disk-usage-report' to generate this file.
I am using Fedora 14 with a version of greyhole newer than the required 0.9.29:
Code: Select all
[root@amahi greyhole]# uname -r; rpm -q samba hda-greyhole
2.6.35.6-45.fc14.x86_64
samba-3.5.5-68.fc14.1.x86_64
hda-greyhole-0.9.31-1.x86_64Code: Select all
[root@amahi greyhole]# greyhole
greyhole, version 0.9.31, for linux-gnu (noarch)
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v3 license.
Usage: greyhole [ACTION] [OPTIONS]
Where ACTION is one of:
-?, --help Display this help and exit.
-D, --daemon Start the daemon.
-P, --pause Pause the daemon.
-R, --resume Resume a paused daemon.
-f, --fsck Schedule a fsck.
-C, --cancel-fsck Cancel any ongoing or scheduled fsck operations.
-l, --balance Balance available space on storage pool drives.
-B, --cancel-balance Cancel any ongoing or scheduled balance operations.
-s, --stats Display storage pool statistics.
-i, --iostat I/O statistices for your storage pool drives.
-L, --logs Display new greyhole.log entries as they are logged.
-S, --status Display what the Greyhole daemon is currently doing.
-q, --view-queue Display the current work queue.
-a, --empty-trash Empty the trash.
-b, --debug=filename Debug past file operations.
-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.
-r, --replace[=path] Tell Greyhole that you replaced the drive at <path>.
-X, --fix-symlinks Try to find a good file copy to point to for all broken
symlinks found on your shares.
-p, --delete-metadata<=path>
Delete all metadata files for <path>, which should be a
share name, followed by the path to a file that is gone
from your storage pool.
-U, --remove-share<=share_name>
Move the files currently inside the specified share from the
storage pool into the shared folder (landing zone),
effectively removing the share from Greyhole's storage pool.
For --stats and --view-queue, the available OPTIONS are:
-j, --json Output the result as JSON, instead of human-readable text.
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-metadata-store
Speed up fsck by skipping the scan of the metadata store
directories. Scanning the metadata stores is only required to
re-create symbolic links that might be missing from your
shared directories.
-c, --if-conf-changed Only fsck if greyhole.conf or smb.conf paths changed since
the last fsck.
Used in the daily cron to prevent unneccesary fsck runs.
-d, --dir=path Only scan a specific directory, and all sub-directories.
The specified directory should be a Samba share, a
sub-directory of a Samba share, or any directory on a
storage pool drive.
-o, --find-orphaned-files
Scan for files with no metadata in the storage pool drives.
This will allow you to include existing files on a drive
in your storage pool without having to copy them manually.
-k, --checksums Read ALL files in your storage pool, and check that
file copies are identical. This will identify any problem
you might have with your file-systems.
NOTE: this can take a LONG time to complete, since it will read
everything from all your drives!
-m, --delete-orphaned-metadata
When fsck find metadata files with no file copies, delete those
metadata files. If the file copies re-appear later, you'll need
to run fsck with --find-orphaned-files to have them reappear in
your shares.Can anybody tell me where the problem is?
Thanks!
