Yes, the files will show back up as the fsck rediscovers them. Once the fsck is done all the files should be back. Is this same fsck that you started a few days ago still running?

I thought you had seen the queue going down. Now it's growing? What exactly are you storing on the pool that is pushing through so many file operations?

You know, I thought that the spool files were the pending tasks... so, I'm not sure the answer there. Am I misunderstanding the nature of the spooled files?? There's a difference between pending tasks and the files in the spool directory. Once Greyhole reads a spool file and loads that task into th...

You could kill the spooled files, but there are a few caveats to that. Greyhole will lose any knowledge of file operations that were performed and are represented in those spool files. (i.e. any renames, moves, deletes, writes, etc) Most of those don't carry much risk, if you moved or renamed someth...

You were absolutely right, found the culprit and removed bloody script. Any suggestion for the second point: How can I set the system to send an email if such kind of problems occur? It's actually already sending emails. :) But the mail is likely only going to your local server mailbox which isn't ...

How would Greyhole know if a file was written to or modified in a particular share or not? I thought the fsck would just detect the moved/renamed symlinks and then modify the tombstone and file accordingly, but I must not understand the moving/renaming process in Greyhole properly. Moves/renames/mo...

You can't nest shares when dealing with Greyhole. Ostensibly it seems like you could as Greyhole won't know about file operations to the child directory, but whenever Greyhole goes through and runs an fsck it will go through its entire landing zone, including the child directory owned by your nested...

Glad to hear it. Just to loop things around for anyone else that happens to read this thread, I sent a PM to Vertigo500 and instructed him to remove all tombstones. (i.e. for each graveyard `rm -r /path/to/pool/drive/gh/.gh_graveyard/*` -- and the backup graveyards as well!) and then run an fsck wit...

The error is pretty straight forward, it's not finding that directory. I doubt it's because the drive is 'slow', more likely it's that the drive has been unmounted for some reason. Next time it happens try to cd to /var/hda/files/drives/drive7/gh and see what happens, I'm betting you'll get the same...

I'm not very familiar with Amahi, so I can't offer any help with questions about it. I use Greyhole with regular Fedora. I'll take a look over the log and let you know what I find.