Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Rackmultipart files not deleted from tmp folder after upload

#3692

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

Reported by Arun R · January 14th, 2010 @ 11:36 AM

State: stale
Milestone: none
Assigned to: nobody
Importance: none

Activity

  1. Claudio Poli
    Claudio Poli

    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...

    February 12th, 2010 @ 07:23 AM

  2. Roland Moriz
    Roland Moriz
    • Tag set to attachment, multipart, rack, upload

    April 11th, 2010 @ 04:47 AM

  3. Roland Moriz
  4. Steven
    Steven

    The same problem is happening to me.

    Rails 2.3.8
    Ruby 1.8.6

    Can anyone confirm this doesn't happen with Ruby 1.8.7?

    July 3rd, 2010 @ 06:26 PM

  5. Tom
    Tom

    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 20090610

    Thanks,
    Tom

    August 19th, 2010 @ 06:35 PM

  6. Santiago Pastorino
    Santiago Pastorino
    • 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.

    February 2nd, 2011 @ 04:59 PM

  7. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:59 PM