VMware Cloud Community
larstr
Champion
Champion
Jump to solution

Upgrade fails with Not enough disk space

Hi,

I'm using vcsa-cli-installer and trying to upgrade from vCenter 6.5U1 to 6.7U1. It is however failing:

2019-06-03 09:01:41,922 - vCSACliInstallLogger - INFO - ================ [FAILED] Task: Running precheck: RecommendOrCheckExportDirTask execution failed at 09:01:41 ================

2019-06-03 09:01:41,928 - vCSACliInstallLogger - DEBUG - Task 'Running precheck: RecommendOrCheckExportDirTask' execution failed because [Not enough disk space on '/' for exporting source data 3.99 GB including migrate set 'core' in export_dir '/storage/updatemgr/temp'.], possible resolution is ['/storage/updatemgr' has sufficient space to accommodate source export data. Provide this as export folder in source_vc.vc_vcsa.export_dir field in template.]

In the vc_vcsa section of my config file I have specified:

"export_dir": "/storage/updatemgr/temp"

The disk space of my source vCenter is as follows:

Filesystem                                Size  Used Avail Use% Mounted on

devtmpfs                                  7.9G     0  7.9G   0% /dev

tmpfs                                     7.9G   20K  7.9G   1% /dev/shm

tmpfs                                     7.9G  688K  7.9G   1% /run

tmpfs                                     7.9G     0  7.9G   0% /sys/fs/cgroup

/dev/sda3                                  11G  7.2G  3.0G  72% /

tmpfs                                     7.9G  1.5M  7.9G   1% /tmp

/dev/sda1                                 120M   28M   87M  25% /boot

/dev/mapper/db_vg-db                      9.8G  5.9G  3.4G  64% /storage/db

/dev/mapper/netdump_vg-netdump            985M  1.3M  932M   1% /storage/netdump

/dev/mapper/seat_vg-seat                   25G  8.8G   15G  38% /storage/seat

/dev/mapper/log_vg-log                    9.8G  4.7G  4.6G  51% /storage/log

/dev/mapper/dblog_vg-dblog                 15G  2.5G   12G  18% /storage/dblog

/dev/mapper/core_vg-core                   50G   52M   47G   1% /storage/core

/dev/mapper/updatemgr_vg-updatemgr         99G  2.8G   91G   3% /storage/updatemgr

/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder

/dev/mapper/autodeploy_vg-autodeploy      9.8G   34M  9.2G   1% /storage/autodeploy

So my /storage/updatemgr has 91G of available disk space which should be more than enough.

Not sure what the easiest method would to proceed here?

Lars

Reply
0 Kudos
1 Solution

Accepted Solutions
larstr
Champion
Champion
Jump to solution

So I crawled the file system and deleted non-critical files and now the upgrade is running.

I wish the root file system had been larger or that the export_dir setting had worked as I thought it would.

Resizing the root file system is not supported by VMware and the unsupported method looks spooky.

Lars

View solution in original post

Reply
0 Kudos
5 Replies
larstr
Champion
Champion
Jump to solution

So I crawled the file system and deleted non-critical files and now the upgrade is running.

I wish the root file system had been larger or that the export_dir setting had worked as I thought it would.

Resizing the root file system is not supported by VMware and the unsupported method looks spooky.

Lars

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Out of curiosity, did you create the temp folder prior to running the migration?

I did an upgrade a few days ago (from the GUI), and specified "/storage/updatemgr" without a sub-directory, which worked.


André

larstr
Champion
Champion
Jump to solution

André,

I think I created the temp directory. I have a pile of vcenters and pscs to upgrade so I'll give it another try the next time I encounter this problem.

Lars

Reply
0 Kudos
jounih
Contributor
Contributor
Jump to solution

I've the same problem.  "export_dir": "/storage/updatemgr/migration" setting on .json file didn't work. I created "migration" folder before the upgrade.

The log shows:

Running precheck: RecommendOrCheckExportDirTask execution failed

Error message: Not enough disk space on '/' for exporting source data 19.34 GB

including migrate set 'all' in export_dir '/storage/updatemgr/migration'.

Any idea how to point exporting source data to "/storage/updatemgr/migration" ?

Jouni

Reply
0 Kudos
jrhaakenson
Enthusiast
Enthusiast
Jump to solution

Can you provide some more details on how you crawled the file system?  I have a VCSA that is doing this for the current 8.0.0-21457384 patch.

Reply
0 Kudos