# Unarchive not using remote\_tmp and filling /tmp

**URL:** <https://forum.ansible.com/t/unarchive-not-using-remote-tmp-and-filling-tmp/24277>\
**Category:** Ansible Project\
**Created:** [April 21, 2017, 6:06am UTC](https://forum.ansible.com/t/unarchive-not-using-remote-tmp-and-filling-tmp/24277 "2017-04-21T06:06:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michele\_Dolfi](https://avatars.discourse-cdn.com/v4/letter/m/aeb1de/32.png) [@Michele\_Dolfi](https://forum.ansible.com/u/Michele_Dolfi)\
**Post date:** [April 21, 2017, 6:06am UTC](https://forum.ansible.com/t/unarchive-not-using-remote-tmp-and-filling-tmp/24277/1 "2017-04-21T06:06:47Z")

</div>

Hello,  
I'm using the unarchive module with a remote URL. Ansible version 2.2.1 and also updated to 2.3.0.

My problem is that the archive I'm downloading is a few GB and the /tmp mount is too small.

I tried to set the ansible\_tmp to a bigger partition. The first Ansible scripts are indeed in the right place, but all they do is unzip the module file in the /tmp folder. The actual module is then downloading the big tarball in the same location, which is not big enough.

Is this really the desired behavior?  
How can I avoid it?

Thanks