Sponsored Content
Operating Systems AIX Map lun info to phyical disks Post 302167619 by roden on Friday 15th of February 2008 02:02:06 AM
Old 02-15-2008
List the disknames with the lsdev command and specify your disktype, examples:
lsdev -Cc disk -t htcuspmpio -Fname # Hitachi
lsdev -Cc disk -t MSYM_RAID -Fname # Emc
lsdev -Cc disk -t mpioosdisk -Fname # IBM generic MPIO

Then you can use the diskname with the lscfg command to get the LUN ID, usually the last part of the location code, example:
lscfg -l hdisk#
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix map?

There is a "Map"? of Unix and all its varients somewhere on the net. I used to have the link , but can't find it now. Anyone out there have a clue???? A good magician never reveals his secret; the unbelievable trick becomes simple and obvious once it is explained. So too with... (3 Replies)
Discussion started by: Bodhi
3 Replies

2. Red Hat

How get more LUN info

Hello, I'm trying to help a guy out on a VMWARE server, running what looks like a cut down version of redhat? 2.4.9-vmnix2 ... Bascially the box serves vm clients via allocating a LUN from a SAN.. to cut a long story short, I need to find out which SAN the luns are comming from (could be 1... (0 Replies)
Discussion started by: itsupplies
0 Replies

3. UNIX for Dummies Questions & Answers

how to get disks info in solaris9

hi: I know its a dummy question do you have any idea how i can get information about the HDs I have on my solaris server?? like how many disks and the size of each?? the prtdiag doesnt tell about disks. Thanks (8 Replies)
Discussion started by: aladdin
8 Replies

4. Solaris

LUN / Diskgroup info

Hi, I was just about to decommission a box when a weird question paused the operation. This box has veritas volume manager installed. I was umounting all the vx volumes and deleting the disk groups so that the storage admin can take back the LUNS. Now this is where i am stuck - i see a disk... (0 Replies)
Discussion started by: s4g3
0 Replies

5. Solaris

I have LUN ID, how to find disk relate to that LUN ID?

I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer. thanks (4 Replies)
Discussion started by: uuontario
4 Replies

6. Solaris

Solaris raw disks info

Hi, I need the following information. 1. We have raw disks but how to identify raw disks. Is there any command to identify its type and size. 2. How to differentiate between disks which are used as file system and that are still available to be used as raw. I know we can use df -n to... (7 Replies)
Discussion started by: malikshahid85
7 Replies

7. Programming

Map Question C++

Hello All, I am having an issue of putting a Boolean value in the maps as the 3rd parameter. Something like the following : int value; std::map<String str, int x, bool bl> where bool returns false if x>value else true. All I see in the map examples is that I can add the... (2 Replies)
Discussion started by: mind@work
2 Replies

8. Solaris

Restore of Netapp FC lun targets used as the disks for a zpool with exported zfs file systems

So, We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies

9. Solaris

Solaris 10 Sparc. How to change Vendor info of SAN disks reported in "format" command?

Greetings! After block level migration using an external appliance, the luns are getting reported as DGC-RAID5 and these luns are infact from the new storage. I have a query on changing the device Vendor info from DGC-RAID5 to HP3par in the format o/p only. AVAILABLE DISK SELECTIONS: ... (3 Replies)
Discussion started by: n_Bhaskar
3 Replies
DISKLIST(5)						   File formats and conventions 					       DISKLIST(5)

NAME
disklist - List of partitions to back up for Amanda DESCRIPTION
The disklist file determines which disks will be backed up by Amanda. The file usually contains one line per disk: hostname diskname [diskdevice] dumptype [spindle [interface] ] All pairs [ hostname diskname ] must be unique. Lines starting with # are ignored, as are blank lines. The fields have the following meanings: hostname The name of the host to be backed up. If diskdevice refers to a PC share, this is the host Amanda will run the Samba smbclient program on to back up the share. diskname The name of the disk (a label). In most case, you set your diskname to the diskdevice and you don't set the diskdevice. If you want multiple entries with the same diskdevice, you must set a different diskname for each entry. It's the diskname that you use on the commandline for any Amanda command. Look at the example/disklist file for example. diskdevice Default: same as diskname. The name of the disk device to be backed up. It may be a full device name, a device name without the /dev/ prefix, e.g. sd0a, or a mount point such as /usr. It may also refer to a PC share by starting the name with two (forward) slashes, e.g. //some-pc/home. In this case, the program option in the associated dumptype must be entered as GNUTAR. It is the combination of the double slash disk name and program GNUTAR in the dumptype that triggers the use of Samba. dumptype Refers to a dumptype defined in the amanda.conf file. Dumptypes specify backup related parameters, such as whether to compress the backups, whether to record backup results in /var/lib/dumpdates, the disk's relative priority, etc. spindle Default: -1. A number used to balance backup load on a host. Amanda will not run multiple backups at the same time on the same spindle, unless the spindle number is -1, which means there is no spindle restriction. interface Default: local. The name of a network interface definition in the amanda.conf file, used to balance network load. Instead of naming a dumptype, it is possible to define one in-line, enclosing dumptype options within curly braces, one per line, just like a dumptype definition in amanda.conf. Since pre-existing dumptypes are valid option names, this syntax may be used to customize dumptypes for particular disks. A line break must follow the left curly bracket. For instance, if a dumptype named normal is used for most disks, but use of the holding disk needs to be disabled for the file system that holds it, this would work instead of defining a new dumptype: hostname diskname [ diskdevice ] { normal holdingdisk never } [ spindle [ interface ] ] The { must appear at the end of a line, and the } on its own line possibly followed by the spindle and interface. SEE ALSO
amanda(8), amanda.conf(5) The Amanda Wiki: : http://wiki.zmanda.com/ AUTHORS
James da Silva <jds@amanda.org> Stefan G. Weichinger <sgw@amanda.org> Dustin J. Mitchell <dustin@zmanda.com> Zmanda, Inc. (http://www.zmanda.com) Amanda 3.3.1 02/21/2012 DISKLIST(5)
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy