標題: [軟件] VMWARE HOW TO FIX IT No free space left on device (1007638 )NOW [打印本頁] 作者: 愚生 時間: 2014-11-15 12:43 標題: VMWARE HOW TO FIX IT No free space left on device (1007638 )NOW
ESXi/ESX error: No free space left on device (1007638)
If a filesystem has unused space on it, but the number of inodes has reached the maximum, no new files can be created. This can appear like a full filesystem.
You must determine if the ESX console file system and the VMFS file system have reached the inode or filesystem limit.
To determine if the ESX console file system and the VMFS file system have reached the inode or filesystem limit:
1.Gain root access to the command line.
◦For ESX, open a SSH session.
◦For ESXi, see Tech Support Mode for Emergency Support (1003677)
.
In this example, there are 640000 inodes total and 580065 are free, so there are inodes available.
3.If, however, you have exhausted the inode limit, you must remove some files. To free some space, see Freeing disk space on an ESX Server in Investigating disk space on an ESX or ESXi host (1003564) or Freeing ESXi inodes (1008643).
To generate a list of log files that may be candidates for deletion, run:
find / -path "/vmfs" -prune -o -type f -size +50000k -exec ls -l '{}' \;
This command seeks out files 50,000 KB (50MB) or larger, skips the /vmfs directory where virtual machines may be located, and provides detailed output for each file. This may return locally-stored ISO files, log bundles, large log files, etc.
Some typical paths where excess files may be located are:
◦/tmp/vmware-root
◦/var/core
◦/var/log/vmware/aam/rule
Warning:
◦Carefully review the files in question before removal using rm. Files cannot be recovered after deletion.
◦Do not delete log information unless absolutely necessary. Consider archiving older logging elsewhere.
4.Run the following command against the VMFS volume:
