Unable to delete files

[NeverSimple]

Hello,

In one of my shares, which is part of the greyhole storage pool, I can't seem to erase a subdirectory. Or actually, I can erase it but it keeps coming back.
I don't even know how that subdirectory got there: It's got the same name as it's parent (but in lower case, whereas it's parent uses uppercase) and holds partly the same files. I assume I did something wrong, but got no idea what. Anyway, I want to get rid of it. First I tried erasing from a windows client and eventually with a SSH login directly on the server (in /var/hda/files, NOT on the disks which are part of the greyhole pool). In both cases the subdir, including all files are gone but (I assume after a 'greyhole --fsck) there back. I'm not sure if this is limited to only this subdir, I haven't really deleted much files.

I'm using:
platform: 5.5.1-21
core:3.5.1.-1
hda-greyhole:0.6.12

Richard

[gboudreau]

Trying to play in any file in /var/hda/files manually is not a good idea.
See the Important Warnings section here: http://wiki.amahi.org/index.php/Greyhole

Second, your greyhole version is very old. The latest is 0.6.26.
Greyhole should be updated automatically with hdactl and hda-platform (there's a check every hour). So unless you manually disabled that, there is something wrong with the hda* auto-updates on your system.
Fix that, (or manually upgrade to hda-greyhole 0.6.26), then try again.

Cheers.

[NeverSimple]

Trying to play in any file in /var/hda/files manually is not a good idea.
See the Important Warnings section here: http://wiki.amahi.org/index.php/Greyhole

Okay, I see. Still got a lot to learn and trying to get a grasp on how greyhole is integrated in the system.

Second, your greyhole version is very old.

Actually, it isn't . I did a quick 'yum info hda-greyhole' and read the results wrong. I Only saw the 'available package' message (which says 0.6.12) and missed the 'installed package' message, which is 0.6.26. Pfff.

Another embarrassing discovery: The files coming back after deletion are probably due to an external computer sync'ing with this share.This was setup as a quick test some time ago and I forgot all about it.

I guess the lesson learned is: stop and think before you post..... (yeah, right )

Anyway, thanks for your response Guillaume,

Richard