2. The content of the /etc/samba/smb.conf & /etc/greyhole.conf files (provide paste URLs):

3. The result of the following commands:

4. The list drives in your storage pool (per Amahi platform):

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):

6. The Greyhole work queue:

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:

I've not seen too many other reports of this occuring on the internet, so I suspect it's something that may be specific to my setup. However, the fix is pretty general, so I'm documenting it here for others to use.

Stop the greyhole daemon<br />

Connect to the MYSQL engine

Select the Greyhole database

Drop and Recreate the 'Tasks' table with the same structure

Exit the MYSQL engine

Restart the greyhole daemon<br />

Schedule an fsck to clear out the files currently in the landing zone

If you've done the above, and all you've accomplished is another stuck fsck, it's time to get serious. The only solution I've found is to blow away the landing zone and then schedule the fsck with an empty landingzone. Greyhole will rebuild your file links from the files in your storage drives, so you won't lose anything except the data that was waiting to be moved to your storage drives. The steps below will mitigate even that loss.

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.

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.

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.

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.

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.

'''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.

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).