Deleting big files

[Andreas Richter]

I uploaded a zipped file of nearly 6 GB. I want to delete it permanently now. I can delete it and push it into the trash, but it is not possible to delete it permanently. An error message pops up.

Can I go around the backend and access the server via FTP and delete it without causing any damage to the DB? Or what would be the best way to do it?

Best Andreas

[Mike Perry]

Not sure I understand. Are you deleting the resource on the individual Resource view page then permanently deleting it from the View resources | View deleted resources page?

What do you mean by 'push it into the trash'? What error message do you get? Is this a Linux server?

[Andreas Richter]

I want to permanently delete a resource exactly as you have described it. T. Step: delete resource on the Resource view page. 2 Step: Go to deleted resources, search for the deleted resource and permanently delete it.

If I do the second step I receive the following error message:

500 Internal Server Error
URL: https://dam.museum4punkt0.de/pages/delete.php?ref=356&search=&offset=0&order_by=relevance&sort=DESC&archive=3&restypes=&ajax=true&posting=true
POST data: ref=356&CSRFToken=4ab2a467e8d11a26e74fbf6c39b72b1c23185157b082a43d02879b73b82b2b4c%40%40a29e70c6e74c76c82281bd5891d9da41e2ded65c3cd7228150af2b8c601edb226eb20022481fc36537b337a28a197e6e326e7b86824fdd5a93f37b1cbee65b0b18e6f2f48103c32d5451760089e1454aa6f6e8464c1389c4fcb1edb498b335ed139aca92cfa0773d2de65ff54b4aba4823ea9fef572c3fb8bdd6c6ee8346f3e144e8bfe1ed01612a9064c398a9b7c20440bd831466a30a2987125879d237137db5a62454e7f8bf9eed143587%40%403e3059d90dad3df744e6fa3d5ffcbede3fffd754e8409342adf29d2e4b26040a&save=true

--
ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.com
---
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/resourcespace/75535d86-1ca1-46b9-8357-28124e7a7941n%40googlegroups.com.

[Ronnie Zeiller]

Hi,

if you can delete other (smaller) files via RS in the described way
and you do not have other large files where the same problem could appear
and you checked if it is not a permission problem,
then I would do:

Rename the large file.
Load a small dummy to the server and give it the name of the file you want do delete.
Check permissions.
Delete the file in RS.

When everything is fine then you delete the 6GB file.

[Andreas Richter]

Many thanks Ronnie for the advice. I followed your proposal my answers in between:

Yes, I can delete other (smaller) files via RS in the described way
and you do not have other large files where the same problem could appear. No, I uploaded the same file again, after renaming the first, and I could permanently delete it
and you checked if it is not a permission problem, I was the contributor of the file. I should have the permission. How can I check permission rights on the Backend? (I'm registered as Super Admin as a user, but I do not have direct access to the server)
then I would do:

Rename the large file.
Load a small dummy to the server and give it the name of the file you want do delete.
Check permissions.

Delete the file in RS. This was no problem at all.

When everything is fine then you delete the 6GB file. Still not possible.

Any other idea, what I can dio?

Best Andreas

To view this discussion on the web, visit https://groups.google.com/d/msgid/resourcespace/b4d2b4f8-28f8-45b5-a0b2-b623ea6e4e40n%40googlegroups.com.

[Ronnie Zeiller]

Now everything should be fine with RS and it´s database.

It could also be a disk error....?
Or perhaps a problem with encoding, if the filename contains special characters....?

Try to connect via ssh and cd into the right directory

may be first get (and double check) the right file name by

ls -l 

and then

sudo rm -f filename

will do it?

[Andreas Richter]

Many thanks Ronnie. I will ask our It to do this and get back to you.

Best Andreas

To view this discussion on the web, visit https://groups.google.com/d/msgid/resourcespace/30a128a9-7401-46ea-8203-0f8060cdbf5en%40googlegroups.com.

[Andreas Richter]

The file is actually deleted and not existing anymore, but the resource is still there.

What can be done?

Best Andreas

[Mike Perry]

When you say " the resource is still there" do you mean RS still lists it as a resource?

[Andreas Richter]

Exactly! The resource is listed in the area "deleted files" (see screenshot). And if I run a search. RS will find the resource too.

However the file itself was removed and cannot be located at the server.

 

To view this discussion on the web, visit https://groups.google.com/d/msgid/resourcespace/4499bb9a-86a2-4ce7-882e-937071a1b1e0n%40googlegroups.com.

[Mike Perry]

This sounds as if the resource entry in the Resource table was not deleted.

If you can find the Resource ID for it you can locate that record in the Resource table. You could delete that record; I don't know how that might impact the database integrity since there are records in other resource-related tables that are tied to that ID record.

database_prune.php in the pages/tools folder may cure the related entry issues for the deleted resource record. . .