Root Directory Junk Files

[daaave]

I have an ESXi server that appears to have several junk files in the / (root) directory.

I guess that an erroneous script accidentally created these files, but now I am not sure which I can delete, and which I can remove.

Could anyone post an ls -lah from the / (root) directory of a healthy ESXi 5?

Here is mine:

~ # ls -lah
drwxr-xr-x    1 root     root          512 May 21 17:27 .
drwxr-xr-x    1 root     root          512 May 21 17:27 ..
drwx------    1 root     root          512 Mar 19 17:00 .ssh
drwxr-xr-x    1 root     root          512 Mar 19 16:58 .vmware
drwxr-xr-x    1 root     root          512 Mar 19 16:57 VIB
-rw-r--r--    1 root     root            0 Mar 25 13:50 ],
-rw-r--r--    1 root     root          130 May 21 17:27 admin.log
lrwxrwxrwx    1 root     root           49 Mar 19 16:58 altbootbank -> /vmfs/volumes/4f27627e-4e0a9fa6-aa59-d1b2f75bdf7e
drwxr-xr-x    1 root     root          512 Mar 19 16:57 bin
lrwxrwxrwx    1 root     root           49 Mar 19 16:58 bootbank -> /vmfs/volumes/93381b74-4b5169de-87e0-226971aaca2d
-rw-r--r--    1 root     root            0 Mar 25 13:50 chainId
-rw-r--r--    1 root     root            0 Mar 25 13:50 changeTag
-rw-r--r--    1 root     root            0 Mar 25 13:50 createdTime
drwxr-xr-x    1 root     root          512 May 21 20:35 dev
-rw-r--r--    1 root     root            0 Mar 25 13:50 dynamicType
drwxr-xr-x    1 root     root          512 May 21 17:25 etc
-rw-r--r--    1 root     root            0 Mar 25 13:50 eventTypeId
-rw-r--r--    1 root     root            0 Mar 25 13:50 fullFormattedMessage
-rw-r--r--    1 root     root            0 Mar 25 13:50 host
-rw-r--r--    1 root     root            0 Mar 25 13:50 key
drwxr-xr-x    1 root     root          512 Mar 19 16:57 lib
drwxr-xr-x    1 root     root          512 Mar 19 16:57 lib32
drwxr-xr-x    1 root     root          512 Mar 19 16:57 lib64
-r-x------    1 root     root        14.7k Mar 19 16:56 local.tgz
lrwxrwxrwx    1 root     root            6 Mar 19 16:58 locker -> /store
-rw-r--r--    1 root     root            0 Mar 25 13:50 message
-rw-r--r--    1 root     root            0 Mar 25 13:50 msg
-rw-r--r--    1 root     root            0 Mar 25 13:50 name
-rw-r--r--    1 root     root            0 Mar 25 13:50 objectId
-rw-r--r--    1 root     root            0 Mar 25 13:50 objectName
-rw-r--r--    1 root     root            0 Mar 25 13:50 objectType
drwxr-xr-x    1 root     root          512 Mar 19 16:57 opt
drwxr-xr-x    1 root     root       128.0k May 21 20:35 proc
lrwxrwxrwx    1 root     root           23 Mar 19 16:58 productLocker -> /locker/packages/5.0.0/
-rw-r--r--    1 root     root            0 Mar 25 13:50 reason
-rw-r--r--    1 root     root            0 Mar 25 13:50 root
drwxr-xr-x    1 root     root          512 Mar 19 16:59 sbin
lrwxrwxrwx    1 root     root           49 Mar 19 16:58 scratch -> /vmfs/volumes/507bffff-dca8fff5-b3c5-6cae8b61107b
-rw-r--r--    1 root     root            0 Mar 25 13:50 severity
lrwxrwxrwx    1 root     root           49 Mar 19 16:58 store -> /vmfs/volumes/507bffe8-80d3ace6-f499-6cae8b61107b
drwxr-xr-x    1 root     root          512 Mar 19 16:57 tardisks
drwxrwxrwt    1 root     root          512 May 21 20:34 tmp
-rw-r--r--    1 root     root            0 Mar 25 13:50 userName
drwxr-xr-x    1 root     root          512 Mar 19 16:57 usr
-rw-r--r--    1 root     root            0 Mar 25 13:50 value
drwxr-xr-x    1 root     root          512 Mar 19 16:58 var
drwxr-xr-x    1 root     root          512 Mar 19 16:57 vmfs
drwxr-xr-x    1 root     root          512 Mar 19 16:57 vmimages
lrwxrwxrwx    1 root     root           18 Jun 29  2012 vmupgrade -> /locker/vmupgrade/
-rw-r--r--    1 root     root            0 Mar 25 13:50 }
-rw-r--r--    1 root     root            0 Mar 25 13:50 },
~ #

Thanks

[Dave_Mishchenko · Accepted solution]

Here you go.  The root folder is a RAM disk so if you reboot the host it'll recreate the directory structure and that should clean things up for you.

~ # ls -lah

drwxr-xr-x 1 root root 512 May 22 04:22 .

drwxr-xr-x 1 root root 512 May 22 04:22 ..

-rw------- 1 root root 8 May 22 04:22 .ash_history

-r--r--r-- 1 root root 20 Aug 2 2012 .mtoolsrc

drwxr-xr-x 1 root root 512 May 18 18:28 .vmware

lrwxrwxrwx 1 root root 49 May 17 12:16 altbootbank -> /vmfs/volumes/aee578ec-4c0a4525-6b2d-2e700ad1644e

drwxr-xr-x 1 root root 512 May 17 12:17 bin

lrwxrwxrwx 1 root root 49 May 17 12:16 bootbank -> /vmfs/volumes/bed7fdea-7d0d9368-cbaf-64a81eb4ab75

-r--r--r-- 1 root root 293.0K Aug 2 2012 bootpart.gz

drwxr-xr-x 1 root root 512 May 22 04:23 dev

drwxr-xr-x 1 root root 512 May 17 12:16 etc

drwxr-xr-x 1 root root 512 May 17 12:17 lib

drwxr-xr-x 1 root root 512 May 17 12:17 lib64

-r-x------ 1 root root 23.2K May 16 17:01 local.tgz

lrwxrwxrwx 1 root root 6 May 17 12:17 locker -> /store

drwxr-xr-x 1 root root 512 May 17 12:17 mbr

drwxr-xr-x 1 root root 512 May 17 12:17 opt

drwxr-xr-x 1 root root 128.0K May 22 04:23 proc

lrwxrwxrwx 1 root root 22 May 17 12:17 productLocker -> /locker/packages/5.1.0

drwxr-xr-x 1 root root 512 May 17 12:17 sbin

lrwxrwxrwx 1 root root 57 May 17 12:17 scratch -> /vmfs/volumes/4fc9cd70-69c49f15-82a1-003048db6889/.locker

lrwxrwxrwx 1 root root 49 May 17 12:16 store -> /vmfs/volumes/4fc9b582-d4868361-534e-003048db6889

drwxr-xr-x 1 root root 512 May 17 12:17 tardisks

drwxr-xr-x 1 root root 512 May 17 12:17 tardisks.noauto

drwxrwxrwt 1 root root 512 May 22 04:01 tmp

drwxr-xr-x 1 root root 512 May 17 12:17 usr

drwxr-xr-x 1 root root 512 May 17 12:17 var

drwxr-xr-x 1 root root 512 May 17 12:17 vmfs

drwxr-xr-x 1 root root 512 May 17 12:17 vmimages

lrwxrwxrwx 1 root root 17 Aug 2 2012 vmupgrade -> /locker/vmupgrade

[daaave]

Thanks!