mapping device from an inq output to veritas disk groups


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting mapping device from an inq output to veritas disk groups
# 1  
Old 01-06-2009
mapping device from an inq output to veritas disk groups

Hi, Does anyone have a clever way of mapping the following from two different files using perl.

sample line from vxdisk list output (vxdisk-list.file):

emcpower18s2 auto:sliced IDFAG1_1 (IDFAG1_appdg) online


sample line from 'inq' output (inq.file):


dev/rdsk/emcpower18c :EMC :SYMMETRIX :5670 :280076a000 : 8923200 :000287750328


I would like the resulting output to appear in
the following format

Diskgroup Device ID
======= =======
IDFAG_appdg, 280076a000

Many Thanks,
Collin
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies

2. Linux

Logical Volume to physical disk mapping

When installing Linux, I choose some default setting to use all the disk space. My server has a single internal 250Gb SCSI disk. By default the install appears to have created 3 logical volumes lv_root, lv_home and lv_swap. fdisk -l shows the following lab3.nms:/dev>fdisk -l Disk... (2 Replies)
Discussion started by: jimthompson
2 Replies

3. Solaris

T5220 disk mapping issue

Hi, More a Sun T5220 problem then a Solaris 10 problem, but perhaps someone had a similar issue. For starters the output with 1 disk in slot 0 of the server. It points to PhyNum 5, where I would expect PhyNum 0. {0} ok probe-scsi MPT Version 1.05, Firmware Version 1.22.00.00 Target... (2 Replies)
Discussion started by: ejdv
2 Replies

4. Solaris

Veritas not attaching replaced disk

Hi, I`m on SunFire480R with Solaris 10. Disk in rootdg group failed, so it was replaced. However, I cannot make Veritas initalise the replaced disk: # vxdctl enable # vxdisk list c1t0d0s2 Device: c1t0d0s2 devicetag: c1t0d0 type: auto flags: online error private autoconfig... (1 Reply)
Discussion started by: masloff
1 Replies

5. UNIX for Dummies Questions & Answers

Configure disk group with veritas

People i have an a storage i create two virtual disk 1 y 2. In the virtual disk 1 i configure 8 volumes and in the Vd2 configure 5 volumes. Now i want to create a disk group called Prod2 y Dev2 but when i go to vxdiskadm and i choose add disk o encapusalte when i press list to list the disk... (0 Replies)
Discussion started by: enkei17
0 Replies

6. AIX

Problem mapping LUN disk from VIOS to the LPAR

Hello guys, It would be so nice of you if someone can provide me with these informations. 1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Discussion started by: solaix14
3 Replies

7. AIX

LPAR and vio disk mapping

We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies

8. Solaris

OpenSolaris 2008.11 Hard Drive Device mapping

Dear Solaris Experts, I am a bit confused about OpenSolaris Hard Drive device mapping. On RedHat Linux based system, an IDE on first channel master drive is mapped as /dev/hda, first channel slave drive will be /dev/hdb, etc. For (Open)Solaris systems I found it as /dev/rdsk/c3d0p0 : ... (0 Replies)
Discussion started by: Zepiroth
0 Replies

9. Solaris

Need to remove a disk from Veritas

I have a bogus disk that keeps showing up as failed from vxdisk list - - disk hpdg failed was:c2t0d11s2 There isnt any c2 devices on the system: # ls /dev/dsk/c2* /dev/dsk/c2*: No such file or directory # ls /dev/rdsk/c2* /dev/rdsk/c2*: No such file or... (3 Replies)
Discussion started by: kiem
3 Replies

10. Filesystems, Disks and Memory

FSCK on veritas managed disk

I've had a VXFS filesystem get corrupted and now it won't mount. Can I run a fsck -y on the raw disk device or should something be done within veritas? Veritas does not see the disk at the moment. (2 Replies)
Discussion started by: ozzmosiz
2 Replies
Login or Register to Ask a Question
IMEDIFF2(1)															       IMEDIFF2(1)

NAME
imediff2 - An interactive fullscreen 2-way merge tool SYNOPSIS
imediff2 [-m] [-u] [-a] [-b] [-c] [-N new-file] [-o outputfile] {file1} {file2} DESCRIPTION
Merge two (slightly different) files interactively with a user friendly fullscreen interface in text mode. Imediff2 shows the differences of given two files (in color if the terminal supports them), lets you scroll the file and toggle changes be- tween old and new version one by one. If the 'unresolved' mode is enabled, you can optionally save both versions. Additionally, if the $EDITOR environment variable is set or if /usr/bin/editor exists and is executable, you can also launch an external editor and manually edit the half-merged file before saving it, perhaps to resolve the 'unresolved' parts. Empty lines are shown in reverse colors so you see that you can select them. If a line is missing completely from one file, imediff2 dis- plays it as a reversed '?'. While it seems to take one line in the editing phase, it is naturally not saved into the output file. To see a list of keyboard commands, hit h or ? in the editor. The program exits with status 0 if the changes were saved, 1 if the merging was aborted and 2 if the parameters were invalid. OPTIONS
-o outputfile, --output=outputfile Write output to given file. If missing, changes will not be saved. -N, --new-file Treat absent files as empty. -m, --mono Force monochrome display. -u, --unresolved Enable 'unresolved' mode (see above). -a Start with version A (default). -b Start with version B. -c Start with unresolved changes (implies -u). -h, --help Show summary of options and exit. -V, --version Show version and exit. KEYBOARD COMMANDS
The following keyboard commands are available in the editor. h, ? Show commands. up, down, left, right Move in document. page up, page down Move a screenfull. enter Toggle selected change. n, tab, space Jump to next change. p Jump to previous change. a Set current chunk to version A. b Set current chunk to version B. u Set current chunk to unresolved. shift+a Set all changes to version A. shift+b Set all changes to version B. shift+u Set all changes to unresolved. e Launch external editor. r Discard editor-made changes. (Available only after e.) x, s Save and exit. q, ctrl+c Exit without saving. home, end Jump to start or end. SEE ALSO
sdiff (1), diff (1), merge (1), diff3 (1). COPYRIGHT
This manual page as well as the program itself was written by Jarno Elonen (<elonen@iki.fi>). Unlike the program itself, which is licensed under the GNU General Public License (GPL) version 2 (or any later version, at your option), this document has been placed into the Public Domain. AUTHOR
Jarno Elonen. 2006-03-10 IMEDIFF2(1)