Try using df to watch the local filesystems while the upload is running. If
you bump 100% anywhere you have the culprit. Either fix that, more space or
a link to a filesystems with more space. Or alternatively put the v202
image on a web server and use the url. That way all the processing is done
on the director.

On Sun, 18 Oct 2015 8:07 am Parthiban Annadurai <senjiparthi(a)gmail.com>
wrote:

Hello John,
Based on your suggestions, I tried to upload from /tmp. Still
it throws the Error. For your Reference I have attached the ScreenShot.
Could you please take a look on that? Thanks.

Regards

Parthiban A

On 12 October 2015 at 09:14, Parthiban Annadurai <senjiparthi(a)gmail.com>
wrote:

John, Thanks for your suggestions. Let me try with /tmp.

Regards

Parthiban A

On 11 October 2015 at 22:59, John Feminella <jfeminella(a)pivotal.io>
wrote:

It looks like you are trying to upload a release from a local file on
your system called /root/tmp/cf-release-202.tgz.

It also looks like you mounted this path at /. However, you appear to
only have 114M available free space here:

/dev/mapper/VolGroup00-LogVol00_root
2.1G 1.9G 114M 95% /

and this logical volume is 95% full. That will not be enough space to
extract the files -- cf-release-202 is ~2 GB compressed so it will take
considerably more space than that to unzip. You may wish to consider
extracting in a location with more free space available (at least 10 GB or
so). Your /tmp mountpoint may be useful, since it looks like that has 16
GiB free.

best,
~ jf

--
*John Feminella*
Advisory Field Engineer
✉ · jfeminella(a)pivotal.io
t · @jxxf <https://twitter.com/jxxf>

On Sun, Oct 11, 2015 at 5:01 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Ronak,
I have checked the Local machine too, it shows the following,

[root(a)opencf microbosh]# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00_root
2.1G 1.9G 114M 95% /
tmpfs 985M 0 985M 0% /dev/shm
/dev/sda1 102M 74M 24M 77% /boot
/dev/mapper/VolGroup00-LogVol00_home
2.1G 3.3M 2.0G 1% /home
/dev/mapper/VolGroup00-LogVol00_opt
6.3G 13M 5.9G 1% /opt
/dev/mapper/VolGroup00-LogVol00_tmp
16G 2.7M 16G 1% /tmp
/dev/mapper/VolGroup00-LogVol00_usr
6.3G 2.0G 4.0G 34% /usr
/dev/mapper/VolGroup00-LogVol00_var
4.2G 126M 3.9G 4% /var

I think size is fine only. Could you?? Thanks.

Regards

Parthiban A

On 11 October 2015 at 14:15, ronak banka <ronakbanka.cse(a)gmail.com>
wrote:

Check "df -h" on your local system from where you are uploading the
release.

On Sun, Oct 11, 2015 at 4:44 PM, Parthiban A <senjiparthi(a)gmail.com>
wrote:

Hi All,
When am uploading the Cloud Foundry Release v202 to the
Director, its throwing the following error.

bosh upload release /root/tmp/cf-release-202.tgz
Acting as user 'admin' on 'microbosh'

Verifying release...
File exists and readable OK
Extract tarball FAILED

Release is invalid, please fix, verify and upload again

My Director VM has more than Enough Free Space in it too.

Sorry, I don't know where to post this issue.

Could anyone please help me on this issue, since am struck with this
more than a week. Thanks

Regards

Parthiban A