Greyhole deleting files that I renamed.

[ATIAdmin]

I was working with a excel document. Called file1.xls let's say. I copy a file2.xls from another directory. Make changes in file2.xls. Deleted file1.xls. Renamed file2.xls to file1.xls. When I open up the newly named file1.xls all of my changes are gone. The file with my changes was moved to the Greyhole attic.

In a similar incident with a Word file. I changed the name of the file and the file disappeared only to be found in the attic.

When I check the greyhole log it seems to be constantly processing files. Is it suppose to do this? I thought it was suppose to run at midnight. Could this constant processing be sending my files to the attic, when I have multiple operations on a file?

[bigfoot65]

How are you accessing files? Via a client or directly on the HDA. If you are accessing files using the HDA, have you implemented the mount_shares_locally script?

Their is also a troubleshooting area in the wiki which might address these concerns.

https://wiki.amahi.org/index.php/Greyhole

[ATIAdmin]

I'm using Windows Explorer when I'm renaming.

[bigfoot65]

Ok, so that should not cause any issues. What version of Greyhole are you using?

[ATIAdmin]

The version of Greyhole is 0.9.22.

[bigfoot65]

Might wanna consider upgrading to 0.9.31 and see if that resolves your issue.

[ATIAdmin]

OK. Thanks

[andyfitter]

FYI, I also had some problems with greyhole. I had it set up with two drives in the pool, and all my shares were set to have two copies, so everything was duplicated across both drives. I was running something called 'bliss' to automatically fix my music metadata

http://www.blisshq.com/

Bliss does a lot of file manipulation - it renames, modifies, creates backups etc. I was finding that a significant proportion of my files (Maybe 2%?) were disappearing when bliss 'fixed' them. The only place they could be found was in the attic, which I had to painfully recover them from.

Bliss was setup to access files through the samba locally mounted shares, so this wasn't the issue. This didn't happen when I tested bliss on the same machine but on a non-greyhole directory.

I never did get to the bottom of it, but now I've turned off greyhole completely, it was more trouble than it was worth in my opinion - Files going missing, poor performance etc.

Now, I still have two drives, but schedule crashplan to do a backup from one to the other every night. This is very slightly less safe, but means that everything behaves the way it should.

[bigfoot65]

May have been a bug that has since been fixed in Greyhole. Amahi is packaged with the latest version of Greyhole at the time of release.

As Greyhole is updated, users have to manually upgrade to the latest version. This is a simple process as documented in the wiki. This is deliberate as automatically upgrading something that messes with the user's data is not wise.

[andyfitter]

Thanks. My HDA is running Fedora 14. At some point in the future I may rebuild and upgrade to something newer, but for now I think I'll stick with what I've got!

Makes perfect sense for you to not auto update Greyhole, but maybe there should be some kind of notification system built into the web interface to let you know that there is a new update available? Possibly you could even have a mechanism for updating through the web UI?

Andy.