How Oracle Works on Exadata - Oracle Exadata Recipes: A Problem-Solution Approach - page 54

FLASH_1_0 FlashDisk 1_0 22.8880615234375G "PCI Slot: 1; FDOM: 0"

FLASH_1_1 FlashDisk 1_1 22.8880615234375G "PCI Slot: 1; FDOM: 1"

FLASH_1_2 FlashDisk 1_2 22.8880615234375G "PCI Slot: 1; FDOM: 2"

... Additional flash disks omitted

CellCLI>

We can see physical disks of type HardDisk with names 20:0 through 20:11 and disks of type FlashDisk grouped
in sections of four per PCI flash card. We also are displaying the LUNs attribute, which shows us the physical disk
to LUN mapping. If you would like to see all details for a physical disk, you can issue a list physicaldisk detail
cellcli command:

CellCLI> list physicaldisk where name=20:2 detail

name: 20:2

deviceId: 17

diskType: HardDisk

enclosureDeviceId: 20

errMediaCount: 0

errOtherCount: 0

foreignState: false

luns: 0_2

makeModel: "SEAGATE ST360057SSUN600G"

physicalFirmware: 0805

physicalInsertTime: 2011-02-21T13:23:43-05:00

physicalInterface: sas

physicalSerial: E1R743

physicalSize: 558.9109999993816G

slotNumber: 2

status: normal

CellCLI>

Oracle builds Exadata LUNs on the usable portions of each physical disk. Using CellCLI , query the LUN details:

CellCLI> list lun attributes name, deviceName, isSystemLun, physicalDrives, lunSize

0_0 /dev/sda TRUE 20:0 557.861328125G

0_1 /dev/sdb TRUE 20:1 557.861328125G

0_2 /dev/sdc FALSE 20:2 557.861328125G

... Additional hard disks omitted

1_0 /dev/sds FALSE FLASH_1_0 22.8880615234375G

1_1 /dev/sdr FALSE FLASH_1_1 22.8880615234375G

1_2 /dev/sdt FALSE FLASH_1_2 22.8880615234375G

... Additional flash disks omitted

CellCLI>

The output displays LUNs for both physical disks and flash disks, the physical device name, TRUE or FALSE
for the isSystemLun attribute, and the LUN size. From the LUN level in the storage hierarchy, the device mapping
simply shows which physical device a LUN is built on; the actual physical partition for the disks in the System Area is
displayed at the cell disk level.