You are not logged in.
Dear,
Today I discovered in the root of one Esxi system lots of *.map.tmp files named after all the files pertaining to 3 different VMs we're backing on that node.
ls -l /win16*
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50-Snapshot8.vmsn.map.tmp
-rw-r--r-- 1 root root 15534080 Oct 19 08:57 /win16-50-flat.vmdk.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.nvram.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.vmdk.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.vmsd.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.vmsd.tmp.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:00 /win16-50.vmx.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.vmx.tmp.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.vmxf.map.tmp
-rw-r--r-- 1 root root 41 Oct 19 08:57 /win16-50.vmx~.map.tmp
Why are they there?
thanks
regards,
Offline
That was due to a bug we fixed in earlier 1.5 branch. You can safely delete them if you are using 1.5.1.3. There's nothing more to it than the inconvenience of the place, it was due to a missing root path. Just run
rm -rf /*.map.tmp
Offline
That was due to a bug we fixed in earlier 1.5 branch. You can safely delete them if you are using 1.5.1.3. There's nothing more to it than the inconvenience of the place, it was due to a missing root path. Just run
rm -rf /*.map.tmp
I need to upgrade then.
thanks,
regards.
Michele
Offline
Yes. 1.5.1.3 is a fairly bug free release.
Offline