Please share the command to get flash doms on 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. :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:-

$ 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):-

$ 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:-

$ 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

$ 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:

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.

Below is the output from the server:

lsdev -Ccdisk
hdisk0 Available  Virtual SCSI Disk Drive
hdisk1 Available  Virtual SCSI Disk Drive
hdisk2 Available  Virtual SCSI Disk Drive
hdisk3 Available  Virtual SCSI Disk Drive
hdisk4 Available  Virtual SCSI Disk Drive
hdisk5 Available  Virtual SCSI Disk Drive
hdisk6 Available  Virtual SCSI Disk Drive
hdisk7 Available  Virtual SCSI Disk Drive
hdisk8 Available  Virtual SCSI Disk Drive

Do you want me to login to VIOS and check the same thing for these lpar?

Best regards,
Vishal

---------- Post updated 04-23-14 at 04:56 AM ---------- Previous update was 04-22-14 at 07:55 PM ----------

Below is the output of this command form vios:

amdc-mgts31vio-ux00: root [/]> lsdev -Cc disk
hdisk0   Available 02-08-00 SAS Disk Drive
hdisk1   Available 02-08-00 SAS Disk Drive
hdisk2   Available 01-00-02 MPIO FC 2145
hdisk3   Available 01-01-02 MPIO FC 2145
hdisk4   Available 01-01-02 MPIO FC 2145
hdisk5   Available 01-01-02 MPIO FC 2145
hdisk6   Available 01-01-02 MPIO FC 2145
hdisk7   Available 01-01-02 MPIO FC 2145
hdisk8   Available 01-01-02 MPIO FC 2145
hdisk9   Available 01-01-02 MPIO FC 2145
hdisk10  Available 01-01-02 MPIO FC 2145
hdisk11  Available 01-01-02 MPIO FC 2145
hdisk12  Available 01-01-02 MPIO FC 2145
hdisk13  Available 01-01-02 MPIO FC 2145
hdisk14  Available 01-01-02 MPIO FC 2145
hdisk15  Available 01-01-02 MPIO FC 2145
hdisk16  Available 01-01-02 MPIO FC 2145
hdisk17  Available 01-01-02 MPIO FC 2145
hdisk18  Available 01-01-02 MPIO FC 2145
hdisk19  Available 01-01-02 MPIO FC 2145
hdisk20  Available 01-01-02 MPIO FC 2145
hdisk21  Available 01-01-02 MPIO FC 2145
hdisk22  Available 01-01-02 MPIO FC 2145
hdisk23  Available 01-01-02 MPIO FC 2145
hdisk24  Available 01-01-02 MPIO FC 2145
hdisk25  Available 01-01-02 MPIO FC 2145
hdisk26  Available 01-01-02 MPIO FC 2145
hdisk27  Available 01-01-02 MPIO FC 2145
hdisk28  Available 01-01-02 MPIO FC 2145
hdisk29  Available 01-01-02 MPIO FC 2145
hdisk30  Available 01-01-02 MPIO FC 2145
hdisk31  Available 01-01-02 MPIO FC 2145
hdisk32  Available 01-01-02 MPIO FC 2145
hdisk33  Available 01-01-02 MPIO FC 2145
hdisk34  Available 01-01-02 MPIO FC 2145
hdisk35  Available 01-01-02 MPIO FC 2145
hdisk36  Available 01-01-02 MPIO FC 2145
hdisk37  Available 01-01-02 MPIO FC 2145
hdisk38  Available 01-01-02 MPIO FC 2145
hdisk39  Available 01-01-02 MPIO FC 2145
hdisk40  Available 01-01-02 MPIO FC 2145
hdisk41  Available 01-01-02 MPIO FC 2145
hdisk42  Available 01-01-02 MPIO FC 2145
hdisk43  Available 01-01-02 MPIO FC 2145
hdisk44  Available 01-01-02 MPIO FC 2145
hdisk45  Available 01-01-02 MPIO FC 2145
hdisk46  Available 01-01-02 MPIO FC 2145
hdisk47  Available 01-01-02 MPIO FC 2145
hdisk48  Available 01-01-02 MPIO FC 2145
hdisk49  Available 01-01-02 MPIO FC 2145
hdisk50  Available 01-01-02 MPIO FC 2145
hdisk51  Available 01-01-02 MPIO FC 2145
hdisk52  Available 01-01-02 MPIO FC 2145
hdisk53  Available 01-01-02 MPIO FC 2145
hdisk54  Available 01-01-02 MPIO FC 2145
hdisk55  Available 01-01-02 MPIO FC 2145
hdisk56  Available 01-01-02 MPIO FC 2145
hdisk57  Available 01-01-02 MPIO FC 2145
hdisk58  Available 01-01-02 MPIO FC 2145
hdisk59  Available 01-01-02 MPIO FC 2145
hdisk60  Available 01-01-02 MPIO FC 2145
hdisk61  Available 01-01-02 MPIO FC 2145
hdisk62  Available 01-01-02 MPIO FC 2145
hdisk63  Available 01-01-02 MPIO FC 2145
hdisk64  Available 01-01-02 MPIO FC 2145
hdisk65  Available 01-01-02 MPIO FC 2145
hdisk66  Available 0B-01-02 MPIO FC 2145
hdisk67  Available 0B-01-02 MPIO FC 2145
hdisk68  Available 0B-01-02 MPIO FC 2145
hdisk69  Available 0B-01-02 MPIO FC 2145
hdisk70  Available 0B-01-02 MPIO FC 2145
hdisk71  Available 01-01-02 MPIO FC 2145
hdisk72  Available 01-01-02 MPIO FC 2145
hdisk73  Available 01-01-02 MPIO FC 2145
hdisk74  Available 01-01-02 MPIO FC 2145
hdisk75  Available 01-01-02 MPIO FC 2145
hdisk76  Available 01-01-02 MPIO FC 2145
hdisk77  Available 01-01-02 MPIO FC 2145
hdisk78  Available 01-01-02 MPIO FC 2145
hdisk79  Available 01-01-02 MPIO FC 2145
hdisk80  Available 01-01-02 MPIO FC 2145
hdisk81  Available 01-01-02 MPIO FC 2145
hdisk82  Available 01-01-02 MPIO FC 2145
hdisk83  Available 01-01-02 MPIO FC 2145
hdisk84  Available 01-01-02 MPIO FC 2145
hdisk85  Available 01-01-02 MPIO FC 2145
hdisk86  Available 01-01-02 MPIO FC 2145
hdisk87  Available 01-01-02 MPIO FC 2145
hdisk88  Available 01-01-02 MPIO FC 2145
hdisk89  Available 01-01-02 MPIO FC 2145
hdisk90  Available 01-01-02 MPIO FC 2145
hdisk91  Available 01-01-02 MPIO FC 2145
hdisk92  Available 01-01-02 MPIO FC 2145
hdisk93  Available 01-01-02 MPIO FC 2145
hdisk94  Available 01-01-02 MPIO FC 2145
hdisk95  Available 01-01-02 MPIO FC 2145
hdisk96  Available 01-01-02 MPIO FC 2145
hdisk97  Available 01-01-02 MPIO FC 2145
hdisk98  Available 01-01-02 MPIO FC 2145
hdisk99  Available 01-01-02 MPIO FC 2145
hdisk100 Available 01-01-02 MPIO FC 2145
hdisk101 Available 01-01-02 MPIO FC 2145
hdisk102 Available 01-01-02 MPIO FC 2145
hdisk103 Available 01-01-02 MPIO FC 2145
hdisk104 Available 01-01-02 MPIO FC 2145
hdisk105 Available 01-01-02 MPIO FC 2145
hdisk106 Available 01-01-02 MPIO FC 2145
hdisk107 Available 01-01-02 MPIO FC 2145
hdisk108 Available 01-01-02 MPIO FC 2145
hdisk109 Available 01-01-02 MPIO FC 2145
hdisk110 Available 01-01-02 MPIO FC 2145
hdisk111 Available 01-00-02 MPIO FC 2145
hdisk112 Available 01-00-02 MPIO FC 2145
hdisk113 Available 01-00-02 MPIO FC 2145

Best regards,
Vishal

I see no SSD here. Are they all hidden in the SAN? If that is the case, then you have to go to the SAN and see what comprises the LUNs it offers to the VIO server.

You may need to use lsmap on the VIO servers to connect each LV (as the VIO sees them) to the hdisks on the user LPAR.

Robin

2145 are SVC's (an inline virtualization), have you asked the storage admin whether they have SSD's (storage array) connected to same SAN as this one? I hope they are NOT playing mix and match on SAS's and SSD's.

I don't know why but I still believe they are all SAS disks.

1 Like

Sorry this is partial/noob answer and nothing harm. But i will check like this.,,

datapath query essmap | grep hdisk4

You will get Which RAID it is from.

Then ask your Storage Person whether this RAIDX is SSD or not.

@Thala
1st thing 1st, do you think ESS has any disk model type 2145? (or for matter 2076)
Also, do you think any command for ESS storage work on SVC?

If I consider, this to be true (which I don't), do you think SVC will give you RAID type? Is it not a logical LUN, carved out of one or more mdisk.

Can you explain me this please.

Oh sorry I didnt notice 2145 !!!