yyyy-mm-ddThh:mm:ss.###Z ERROR vrlcm[#####] [pool-##-thread-##] [c.v.v.l.d.c.t.DownloadFromBroadcomDepot] -- Exception encountered when downloading the binary: No space left on deviceyyyy-mm-ddThh:mm:ss.###Z INFO vrlcm[#####] [http-nio-####-exec-#] [c.v.v.l.u.ShellExecutor] -- Executing shell command: df -h --output=size,used,avail,pcent /data/yyyy-mm-ddThh:mm:ss.###Z INFO vrlcm[#####] [http-nio-####-exec-#] [c.v.v.l.u.ProcessUtil] -- Execute dfyyyy-mm-ddThh:mm:ss.###Z INFO vrlcm[#####] [http-nio-####-exec-#] [c.v.v.l.u.ShellExecutor] -- Result: [Size Used Avail Use% 123G 123G 0 100%].When downloading binaries via Fleet Management, the file is first downloaded to the /data partition and then extracted into a temporary directory within the same partition. Subsequently, the extracted files are placed in the productPatchRepo directory, also located on the /data partition.
As a result, the process temporarily consumes approximately three times the storage space of the original binary size. For large binaries like VCF Automation, this can lead to the exhaustion of the /data partition depending on the available free space prior to the download.
Note: Once the files are successfully placed in the productPatchRepo directory, the initial download file and the temporary files are automatically cleared.
Expand the /data partition or delete any unnecessary binaries to ensure that the available free space is at least three times the size of the binary being downloaded.
Note: As the extraction process consumes disk space equivalent to or exceeding the original file size, please ensure there is ample free space—exceeding three times the binary size—from the perspective of maintaining a safe buffer.
Expanding the /data partition: See "Extending Storage for Binaries" for details.
Removing unnecessary binaries: