Image files not deleting

[jdeguerto]

I too had the same issue. Deleted all images but hdd or node spce was not reclaimed. I even went to /images and deleted the files and didnt reclaim space. Since this is a dev server im testing i ended up formatting the partition where image folder was mounted. I have the same setup as you. Keep me posted and ill try to recreate this tomorrow.

[Tom Elliott]

Does it not remove ANY image data on ANY node or it never deletes any files?

[Wayne Workman]

@Tom-Elliott We’ve only been on RC-14 for a couple days, only one image has been attempted to be deleted so far. None of the image’s files were deleted at all. This particular image isn’t present on other storage nodes, it was only present on the main server.

[Wayne Workman]

More information from the user via email:

Just so you know, when I attempt the deletion of the FOG image, I get a screen to authenticate. After I authenticate, I can see another screen pop up where I could select DELETE or CANCEL, but it disappears so fast that I cannot ever click on DELETE.
Perhaps the programming error is with that second screen that disappears too quickly?

[Tom Elliott]

@Wayne-Workman If the FTP delete is erroring or the page is returning due to mod_evasive, then it’s exiting because it’s done doing the work it can do. That’s it.

[Wayne Workman]

@Tom-Elliott said in Image files not deleting:

mod_evasive

It’s not installed:

[root@acfog ~]# yum remove mod_evasive
Loaded plugins: fastestmirror
No Match for argument: mod_evasive
No Packages marked for removal
[root@acfog ~]#

However it was installed on the node with the “client denied” errors. I’ve removed it.

[Wayne Workman]

I’m currently running a test now with an image that is shared with the node that had mod_evasive, and I’m seeing if it will delete now or not.

[Tom Elliott]

Confirmed the issue and hopefully have it fully addressed now.

It was a bit of an issue, but ultimately very simple. The files were deleting at least on one node (where possible) but failing to iterate due to return which was meant to be changed to a continue.

After finding that out, the issue was the folder for images would still exist (the data would be removed though).

After some fairly thorough testing (I tested what I could, when and where possible) it appears I’ve finally addressed the problem. Trailing folders get removed as well as the contents of those folders.

I’m solving this, and the other, for now. Feel free to keep us posted though.

[Wayne Workman]

@Tom-Elliott but my issue was different, in my case the folder and files remained.

[Tom Elliott]

@Wayne-Workman Yep, and this is also fixed. The files and folders remaining was from order of it doing things. Once it caught a directory of either . or .. it returned without finishing.