New ESXi 5.5 server - how do I tell what physical device my /scratch partition is on?

[PeterBollwerk]

I went to this page - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101495...

But unfortunately, it doesn't describe how to match the UUID to a physical device.

For example, our server has dual SD cards with embedded ESXi installed and a RAID 1 of 2 SATA drives.

My boss has asked me to make sure the /scratch location is set to the spinning disks, rather than the SD card(s).

I can see what /vmfs/volume/ my /scratch points to, but I have no idea if that volume is on the SD card(s) or spinning disk RAID 1.

I can't find a command that will list each UUID on each physical drive.

It doesn't help that I'm not much of a linux guru. =/

[MGlasson]

go to configuration-> storage

select your volume and in datastore details you will see an item called extents,

where it will list the physical details of the disks being used for that datastore.

[Shrikant_Gavhan · Accepted solution]

Hi PeterBollwerk,

Below steps would show you the location of scratch on your esxi host. in this example my esxi is running on a dual SD card in mirror.

~ # ls -ltr

-r--r--r--    1 root     root        300060 Mar 23  2013 bootpart.gz

lrwxrwxrwx    1 root     root            17 Mar 23  2013 vmupgrade -> /locker/vmupgrade

drwxr-xr-x    1 root     root           512 Feb 12 09:58 vmimages

drwxr-xr-x    1 root     root           512 Feb 12 09:58 vmfs

drwxr-xr-x    1 root     root           512 Feb 12 09:58 var

drwxr-xr-x    1 root     root           512 Feb 12 09:58 usr

drwxr-xr-x    1 root     root           512 Feb 12 09:58 tardisks.noauto

drwxr-xr-x    1 root     root           512 Feb 12 09:58 tardisks

drwxr-xr-x    1 root     root           512 Feb 12 09:58 opt

drwxr-xr-x    1 root     root           512 Feb 12 09:58 mbr

drwxr-xr-x    1 root     root           512 Feb 12 09:58 lib64

drwxr-xr-x    1 root     root           512 Feb 12 09:58 lib

drwxr-xr-x    1 root     root           512 Feb 12 09:58 bin

lrwxrwxrwx    1 root     root            49 Feb 12 09:59 store -> /vmfs/volumes/52fb429d-994d220a-479f-18a99b4c7caf

lrwxrwxrwx    1 root     root            49 Feb 12 09:59 bootbank -> /vmfs/volumes/92a34de2-91752a9b-98b3-d172a66e7716

lrwxrwxrwx    1 root     root            49 Feb 12 09:59 altbootbank -> /vmfs/volumes/4eb69ee7-d8084e62-87e9-ff614e70bdf4

lrwxrwxrwx    1 root     root            12 Feb 12 09:59 scratch -> /tmp/scratch

lrwxrwxrwx    1 root     root            22 Feb 12 09:59 productLocker -> /locker/packages/5.1.0

lrwxrwxrwx    1 root     root             6 Feb 12 09:59 locker -> /store

drwxr-xr-x    1 root     root           512 Feb 12 09:59 sbin

drwxrwxrwt    1 root     root           512 Feb 21 12:06 tmp

drwxr-xr-x    1 root     root           512 Feb 21 12:06 etc

drwxr-xr-x    1 root     root        131072 Feb 21 12:07 proc

drwxr-xr-x    1 root     root           512 Feb 21 12:07 dev

~ # vmkfstools -P /tmp/scratch

visorfs-1.00 file system spanning 1 partitions.

File system label (if any):

Mode: private

Capacity 1556017152 (379887 file blocks * 4096), 1127976960 (275385 blocks) avail

UUID: 00000000-00000000-0000-000000000000

Partitions spanned (on "notDCS"):

        memory

Is Native Snapshot Capable: NO

In case if you have not configured your esxi to put logs on a persistent scratch location, it stays in the memory.

Hope this helps you.

Thanks and Regards,

Shrikant Gavhane

[homerzzz]

This article shows how to determine the scratch location and how to configure it. No Linux skills needed

Search for this KB

1033696