This project is archived and is in readonly mode.
Rackmultipart files not deleted from tmp folder after upload
Reported by Arun R | January 14th, 2010 @ 11:36 AM
Hi,
I am using attachmentfu to upload files. We are upoading files of size more than 50MB. While uploading, rackmultipartxxxx-xxxx files are created in tmp folder. But after the completion of upload the file still remains in the folder and we are running out of diskspace. From controller, I cannot delete the file as it is locked.
I am using following versions
Jruby 1.3.1
Rails 2.3.4
mongrel 1.1.5
rack 1.0.0
rubyzip0.9.1
Please let me know if you need more information.
Thanks,
Arun
Comments and changes to this ticket
-
Claudio Poli February 12th, 2010 @ 07:23 AM
I'm experiencing the same.
To resolve I'm running tmpreaper on ubuntu do delete temp files older than an hour, but this is only a temporary workaround and not a solution.
I opened a thread about the matter here: http://groups.google.com/group/phusion-passenger/t/c7b5e0f8f0016939...
-
Roland Moriz April 11th, 2010 @ 04:47 AM
- Tag set to attachment, multipart, rack, upload
-
Roland Moriz April 11th, 2010 @ 03:36 PM
see http://groups.google.com/group/rack-devel/browse_thread/thread/6eb2...
(thanks to chneukirchen for providing me a link to that thread)
-
Steven July 3rd, 2010 @ 06:26 PM
The same problem is happening to me.
Rails 2.3.8
Ruby 1.8.6Can anyone confirm this doesn't happen with Ruby 1.8.7?
-
Tom August 19th, 2010 @ 06:35 PM
I am having the same problem where large files (tmp/rackmultipartxxxx-xxxx) are not being cleaned up. I'll do it through CRON, but that is just a rig job.
Rails 2.3.8
ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux]
Ruby Enterprise Edition 20090610Thanks,
Tom -
Santiago Pastorino February 2nd, 2011 @ 04:59 PM
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 04:59 PM
- State changed from open to stale
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>