1. What version of Fedora, Samba & Greyhole are you running?
{{Code| uname -r; rpm -q samba amahi-greyhole}}
2. The content of the /etc/samba/smb.conf & /etc/greyhole.conf files (provide paste URLs):
<blockquote><u>Fedora:</u></blockquote>{{Code| yum -y install fpaste; fpaste /etc/samba/smb.conf fpaste /etc/greyhole.conf}}
<blockquote><u>Ubuntu:</u></blockquote>{{Code| pastebinit /etc/samba/smb.conf pastebinit /etc/greyhole.conf}}
3. The result of the following commands:
{{Code| mount fdisk -l df -h greyhole --stats}}
4. The list drives in your storage pool (per Amahi platform):
{{Code| mysql -u root -phda -e "select * from disk_pool_partitions" hda_production}}
5. A list of the directories on the root of the drives included in your storage pool, obtained with the following command (provide a paste URL):
{{Code|<blockquote><u>Fedora</u></blockquote> mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' | xargs ls -la | fpaste <blockquote><u>Ubuntu<nowiki/u>|</nowikiblockquote> mysql -u root -phda -e "select concat(path, '/gh') from disk_pool_partitions" hda_production | grep -v 'concat(' <nowiki>|</nowiki> xargs ls -la <nowiki>|</nowiki> fpaste}}
6. The Greyhole work queue:
{{Code| greyhole --view-queue}}
If the above command returns nothing, execute the following to see the problem:
{{code| tail /var/log/greyhole.log}}
7. If you have issues with a particular file (file disappeared, is wrong size, has wrong filename), execute the following to find out what Greyhole did with this file:
{{Code| greyhole --debug filename}}
== Clearing The Greyhole Work Queue ==
Stop the greyhole daemon<br />
<blockquote><u>Fedora 19</u></blockquote>{{Code| systemctl stop amahi-greyhole.service}} <blockquote><u>Ubuntu</u></blockquote>{{Code| service greyhole stop}}
Connect to the MYSQL engine
{{Code| mysql -u greyhole -pgreyhole}}
Select the Greyhole database
{{Code| USE greyhole;}}
Drop and Recreate the 'Tasks' table with the same structure
{{Code| TRUNCATE TABLE tasks;}}
Exit the MYSQL engine
{{Code| exit;}}
Restart the greyhole daemon<br />
<blockquote><u>Fedora 19</u></blockquote>{{Code| systemctl start amahi-greyhole.service}} <blockquote><u>Ubuntu</u></blockquote>{{Code| service greyhole start}}
Schedule an fsck to clear out the files currently in the landing zone
{{Code| greyhole --fsck}}
===Queue Still Stuck===
Copy the contents of your landing zone somewhere else (preferably a non-greyhole share, so you can sort it out from the comfort and convenience of your normal workstation). In the example below, I just borrow the AFP share I have locally mounted for Apple timemachine backups, but this can be any folder. Don't copy the /drives subfolder, as that's actually the physical drives attached to the system.
{{Code| cp -rv /var/hda/files/shareName /mnt/timemachine/landingzonebackup/shareName}}
Now, stop the greyhole service again. Do this from the Amahi Console->Settings->Servers->Greyhole. Disable the watchdog and press the big red 'stop' button.
Blow away the contents of your landing zone shares. It is '''very''' important you don't touch the /drives folder within /var/hda/files if you have a default setup.
{{Code| rm -rf /var/hda/files/shareName/*}}
Now, clean up the horrible mess you'll probably have in each drive in /var/hda/files/drives - I had old shares and other assorted crap that was slowing down each fsck. Your /var/hda/files/drives/driveX/gh folder (replace X with whatever drive number you have) should ''only'' have references for your current shares. Use the code below to remove any folders that contain old shares.
{{Code| rm -rf /var/hda/files/drives/drive/gh/folderName}}
Then clean up the even more horrible mess you probably have in your /var/hda/files/drives/driveX/gh/.gh_graveyard folder. ''Note, this is a hidden folder, it won't be listed if you just ls the /var/hda/files/drives/driveX/gh folder.'' Use the command below to remove each folder that isn't a current share.
{{Code| rm -rf /var/hda/files/drives/drive/gh/.gh_graveyard/folderName}}
Now, restart the greyhole service using the Amahi Console. Remember to turn the watchdog back on.
Schedule another --fsck. It should start pretty much right away, and begin rebuilding the landing zone. Note that any shares you have won't be available again until the fsck completes.
{{Code|sgreyhole greyhole --fsck}}
'''Optional''': You'll probably now want to check the landing zone backup you made, and recopy any actual data in the folder back in (don't just copy the whole folder back in, that would make everything you just did pointless).
'''Optional''': Cleaning all the crap out of your physical drives has probably freed up a bit of space (or quite a bit, depending how much crap you have). Now is probably a good time to balance out your storage again.
{{Code|greyhole --balance}}
If you run into any trouble with the above, post it in the [http://forums.amahi.org/viewforum.php?f=39&sid=f676fa2944ab7d2ccfc8901ee731b6fe Amahi forums] '''and''' PM me (U=doczombie) the link to your forum post if you like (PM's without a link to a forum post are liable to be ignored).
===Database Error Table :greyhole.tasks does not exist ===
{{Code| Can't describe tasks with query: DESCRIBE tasks - Error: Table 'greyhole.tasks' doesn't exist}} If the Greyhole service will not start, or you see this message when gathering info for support, it is possible that the Greyhole database was not created. The following MySQL commands will create the database:{{Code| mysql -u root -phda -e 'create database greyhole' mysql -u root -phda -e "grant all on greyhole.* to greyhole@'localhost' identified by 'greyhole'" mysql -u greyhole -pgreyhole greyhole < /usr/share/greyhole/schema-mysql.sql service greyhole restart}}
Back to the [[Greyhole]] page