Two things. First, is /var/hda/files/drives/drive4 the drive that's dying? I see your log has a number of pending tombstones for this drive which is a little odd. Second, it looks like you typo'ed --view-queue as --wiew-queue, can you provide the output of --view-queue? It could be helpful. So far I...

Greyhole will roll its logs once a day, or rather logrotate will do this. Once the log gets to a certain size there can also be issues with Greyhole not being able to open / edit the log file. A huge log file isn't too surprising given the type of load you're running, though. Think about it, if you'...

You'd probably have better luck getting an answer if you asked in a new thread. As to your question, yes, it's possible and common. For instance you can put mount statements in your /etc/rc.local file which will mount your drives by UUID and would not prevent your server from booting if missing a dr...

First off, ext3 is not your issue. It's a pretty rock solid file system. If you can't move files, it's more than likely caused by file permissions, which if you're not familiar with, you should read about. (Check here for a quick primer: http://www.tuxfiles.org/linuxhelp/filepermissions.html ) Secon...

You've got the idea backward for orphaned files. That option looks for files which don't have any tombstones and creates tombstones for them, it does not look for tombstones without file copies. I don't don't think there's a way to clear out barren tombstones. It might be a good feature to request o...

Without seeing your greyhole.conf I can't say for certain, but it looks like you're trying to perform a --going on a location that is not marked as a storage pool drive in your config.

I don't quite follow your 5% math though. You're right about the math, I only glanced quickly at your charts, it should indeed by .05 * 916.9 * 5 = ~230gb of reserved space. (Since your graph shows numbers like 748.7gb free + 168.2gb used = 916.9gb total it's pretty safe to assume that reserved spa...

Yes, I understand that, but the problem is just showing the total used space doesn't really tell us anything. First thing to check, what is the x in 'num_copies[Movies]=x' in /etc/greyhole.conf If that is only 2 as expected, then start going onto the drives see, do you see > 2 copies of the files sp...

What else is on the drives? From my understanding it's just displaying the total used space, not just what Greyhole is taking up.

This should probably be a new thread / question. When you remove a drive and you only have 1x file copies, Greyhole can no longer display your data, you've removed it from your pool. What you need to do is perform a --going on the drive. (Even if you've got > 1 file copies this is still a good idea ...