Bug #618

Greyhole stuck in rename loop - Moving folders within a share

Added by caffeinatedtech almost 11 years ago. Updated almost 11 years ago.

Target version:
Start date:
Due date:
% Done:



Had an issue where I wanted to move folders within a share to reside inside a new folder to create separate folders for financial years and move contents around into the correct folders.

I have this share set to "2 extra copies" in amahi.

Ended up with some folders/files missing from the share. Looked at greyhole log and discovered that it appeared to be doing a "rename: Loading tombstones" over and over on the same set of files.

In an attempt to correct this I:
Rebooted the machine. The log kept rolling through those same files.
Removed and re-added the share from the storage pool by unchecking and rechecking the "use pool" box in amahi.
Ran a fsck on that folder /var/hda/files/Business. This made the missing files come back, but the share was in a mess with some files/folders in the new financial year folder and the rest back out where they started.
cburner recommended I do a --empty-attic as well as doing a fsck with the share out of the pool, then again with it back in the pool.

Now when I try to move folders into the new folder, it creates a copy, but doesn't remove the original. I see errors in the greyhole log saying it failed to unlink.

I looked at the permission on some of the folders under that business share and found that neither "group" nor "other" had write access. Thinking this was the problem, I pushed 777 permissions from the Business folder using the file manager in webmin, verified that permissions had propagated through the share and tried moving folders again.

Now when I move folders, it creates the copy, and leaves empty folders and sub-folders in the original location. Then when I do another move action on that folder, the original (empty) folders disappear.


#1 Updated by gboudreau almost 11 years ago

Try the latest version:
Either rpm -Uvh
or rpm -Uvh

The 0.6.19 version you have installed has issues with directory renames.

To fix permissions, execute this, as root:
(replace your_username with the account which should own the files, and drive_mount_path with the path to your drive)

chown -R your_username:users /drive_mount_path/gh
find /drive_mount_path/gh -type f -exec chmod 664 {} \;
find /drive_mount_path/gh -type d -exec chmod 775 {} \;


chown -R joe:users /var/hda/files/drives/sdb1/gh
find /var/hda/files/drives/sdb1/gh -type f -exec chmod 664 {} \;
find /var/hda/files/drives/sdb1/gh -type d -exec chmod 775 {} \;

Repeat for each of your drives in your storage pool.

#2 Updated by caffeinatedtech almost 11 years ago

gboudreau wrote:

Try the latest version:
Either rpm -Uvh
or rpm -Uvh

Got the following warning about the config file, should I do something about it?

warning: /etc/greyhole.conf created as /etc/greyhole.conf.rpmnew

#3 Updated by gboudreau almost 11 years ago

No. That means the config file that was in the RPM wasn't used, and you old config file was kept instead, which is the expected behaviour.

#4 Updated by caffeinatedtech almost 11 years ago

Performing the recommended actions seems to have fixed the problem. I can now move folders around and the original disappears. I have to refresh the view to see them go, but it is working.

Thank you gboudreau.

#5 Updated by gboudreau almost 11 years ago

  • Category set to setup-storage
  • Status changed from New to Resolved

Marking this resolved in hda-greyhole 0.6.23

Also available in: Atom