Description of problem:
we need to have some cleanup for tmp directory regularly after certain intervals.

[root@gqac022 async_pending]# cd ..
[root@gqac022 AUTH_test]# ls -R cont*
cont1:

cont2:

cont3:

cont4:

cont5:
[root@gqac022 AUTH_test]# ls
async_pending  cont1  cont2  cont3  cont4  cont5  tmp

[root@gqac022 AUTH_test]# du -h tmp/
20G	tmp/


[root@gqac022 AUTH_test]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_gqac022-lv_root
                       50G   25G   23G  52% /
tmpfs                  24G  1.1M   24G   1% /dev/shm
/dev/sda1             485M   31M  429M   7% /boot
/dev/mapper/vg_gqac022-lv_home
                      366G   21G  346G   6% /home
localhost:test        732G   36G  697G   5% /mnt/gluster-object/AUTH_test
[root@gqac022 AUTH_test]# 


Version-Release number of selected component (if applicable):
3.3.0qa45, swift-rc-rpms

How reproducible:
found after creating large number of objects

Steps to Reproduce:
1. create large number of objects  and after a certain time the tmp directory seems to have grown in size
2.
3.
  
Actual results:


Expected results:


Additional info:
if we already have some strategy for cleanup please update about that one.