AIX

Hello,

Please share the command to get flash doms on aix


Best regards,
Vishal

Please explain what problem you are having. I'm assuming that you have searched on the IBM site, but I find nothing relevant. Please confirm what you are looking for or explain the function that is not working.

Do you mean flash prom perhaps, or is it domains? I regret that I'm rather confused.


Robin

The volumes have been migrated to flash(solid state disk) and how do I detrmine at os level that which all file systems have been moved to SSD

I tried with lslv and lspv but could not get much info.Please assist.


Best regards,
Vishal

I understand the "flash" bit, just not the "doms"

The output you are probably looking for will be from lscfg Assuming that you have a volume group of two devices (to make it easy) of which one is real spinning disk and one is SSD, you could get output like this:-

Code:

$ lscfg -vl hdisk1 |grep hdisk
hdisk1           U789C.001.DQD5S24-P2-D4  SAS Disk Drive (300000 MB)

$ lscfg -vl hdisk2 |grep hdisk
hdisk2           U789C.001.DQD5S24-P7-D2  SDD Flash (300000 MB)

Of course you will probably have different disk types, perhaps a RAID device or a SAN LUN assigned.

You will need to check which filesystems are on spinning disk (hdisk1 in my example):-

Code:

$ lspv -M hdisk1

This might produce quite a lot of output, so probably best to catch it to a file. You can then move the logical volumes with migratepv Depending on mirrored LVs and available space on each target disk, you may be better moving each logical volume under your control:-

Code:

$ migratepv -l lv_01 hdisk1 hdisk2

If you are sure that the target disk has sufficient space to do it all in one go, you can just

Code:

$ migratepv hdisk1 hdisk2

The process will probably take a while. Each allocated PP is copied and synced in turn before the old one is removed, whether there is data in it or not, so a 500 Gb filesystem with 200 Mb used will take ages to move, however this can all be done with the filesystem active.

You will have to ensure that if your LV is mirrored, that you do not violate the rules keeping the various partitions separate.



I hope that this helps. For completeness of the thread, it would be good if you can post the output of the disk types.


Kind regards,
Robin

Hello,

Below is the output:

Code:

lscfg -vl hdisk4|grep hdisk
  hdisk4           U8233.E8B.1097BDP-V6-C108-T1-L8500000000000000  Virtual SCSI Disk Drive

Does this mean that this is not on SSD?

Also this hdisk4 comes through SAN Volume controller so how to check for SSD?

Best regards,
Vishal

hmm... somehow the things you state do not add up to a coherent picture.

You can use the "lsattr -El <device>" command to get more information about a device - such as a disk. If your concern is that the SSD disks are visible at all to the system, then this is the way to go. Notice, though, that you will only see directly connected disks this way. What you have shown is a "virtual SCSI" device. I suppose your LPAR got it from a VIOS. You will not be able to see the properties of the physical disk from the LPAR in this case, because it gets the disk without caring where it comes from (just like a file doesn't care what the filesystem it resides at is made from). You will have to log on to the VIOS (or whatever exports the disk - SAN fabric, ...) and look there.

If you have made sure there is a SSD device your system recognizes as a "hdisk" device you may wonder if it is part of a certain volume group. Issue "lspv" in this case and see all the physical volumes along with the volume groups they belong to.

If you are sure a PV is part of a certain VG and wonder if a certain logical volume is on this PV issue a "lslv -m" to get a map file f the LV.

I am still not sure what you are about (you might consider taking a step back, drink a coffee to come down, then explain what your problem is v-e-r-y s-l-o-w-l-y and concisely), but anyway, i hope this helps.

bakunin

Ah! you are using vscsi so you won't really be able to make it out from client which disk is SSD.

Best bet is your VIOS, you can run lsdev -Ccdisk paste the output here.