Sponsored Content
Operating Systems HP-UX Need to make disk device files match Post 302075316 by mvizza on Thursday 1st of June 2006 03:03:05 PM
Old 06-01-2006
Question Need to make disk device files match

Hi,

I was wondering if there was a way to change the disk device files ex. /dev/dsk/cxtxd0 ?

What I have are two HPUX 11.0 servers using MC Service Guard 11.13. A consultant attached a SAN and both servers had created the same identical LUN device files. Now I could begin creating my volume group , lvol, etc. Well, somewhere down the road, before I could config my volume groups, messed up the fiber that was connected to the SAN on one of the servers. After they changed the fiber, I a reconnected, now the HA1 server has different device file numbers then the HA2 server.

Now I know I could just do a vgexport and vgimport and modify the map files etc. but I heard there was a way to change the device files so they would match on both servers. Anyone have any idea?

Thanks,
Mike
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

available disk space on disk device???

Hello, Can someone please tell me which command to use to determine the available disk space on a given disk device? I have to write a shell script that compresses files and stores them in a specific location but I am not sure how "conservative" I should be? Thanks in advance! Al. (4 Replies)
Discussion started by: alan
4 Replies

2. UNIX for Advanced & Expert Users

Swap Device & Unix Disk Buffer

Does anyone know if when the Swap Device / Page file in unix is carrying out Page / Swap In's and Page / Swap outs, does it go through the Unix Disk Cache ( I am presuming raw partitions are not being used ) ? Therefore if there is paging activity on a system ( measured by sar -p, sar -g and... (0 Replies)
Discussion started by: jimthompson
0 Replies

3. Shell Programming and Scripting

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): ... (0 Replies)
Discussion started by: csoesan
0 Replies

4. AIX

rmdev won't remove disk device AIX

Hi all, I'm attempting to remove some EMC hdisk devices which we recently had made available to one of our backup servers. This is an AIX 5.3 server. When I try doing an rmdev I get the following: root@********:/dev# rmdev -d -l hdisk495 Method error (/usr/lib/methods/ucfgdevice): ... (2 Replies)
Discussion started by: C.J.Hund
2 Replies

5. Shell Programming and Scripting

Need help to grep for a title match and then make some queries after the match

Here is the sample of my file address.txt Address 1 1234 Drive way New Orleans, LA Zipcode :- 12345 Address 2 4567 Spring way Chicago, IL Zipcode :- 67890 I would like to grep for an Address title (Ex :- Address 2) , then get its zipcode and echo both in a single line. Ex :- ... (3 Replies)
Discussion started by: leo.maveriick
3 Replies

6. Solaris

Determine free space in a Disk device

Version: Solaris 10 (August 2011) on VM I am kind of new to Solaris.From VM workstation i allocated 35 GB to this Solaris VM's Disk The disk was named c1t0d0 Few basic slices for root(8gb), swap(517mb) and /export/home(494mb) were created by the solaris Installer during the... (18 Replies)
Discussion started by: polavan
18 Replies

7. Shell Programming and Scripting

File representing the hard disk storage device

I want example of a file representing the hard disk storage device In UNIX ? (6 Replies)
Discussion started by: tamer11007
6 Replies

8. Solaris

Cleanup special files create via device match in a whole root zone

I added in the configuration file of a whole root zone the following device match entries: <device match="/dev/rmt/*"/> <device match="/dev/sg/*"/> after the reboot the zone was able to see all the devices of its global zone, and let under /dev/rmt and /dev/sg the special files created with... (1 Reply)
Discussion started by: hugo_perez
1 Replies

9. AIX

Command to check the busy % for a hard disk device like hdisk5

Please help with command to check the busy % for a hard disk device like hdisk5 Best regards, Vishal (7 Replies)
Discussion started by: Vishal_dba
7 Replies

10. Linux

0: Failure: (138) Device does not have a disk-config

Hi guys, Any idea why I am getting the below error ? # drbdsetup disk-options 0 --resync-rate=500M 0: Failure: (138) Device does not have a disk-config Some info is; # fdisk -l Disk /dev/sda: 64.4 GB, 64424509440 bytes 64 heads, 32 sectors/track, 61440 cylinders Units =... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies
vgimport(1M)															      vgimport(1M)

NAME
vgimport - import an LVM volume group onto the system SYNOPSIS
mapfile] vg_name pv_path ... mapfile] infile] vg_name mapfile vg_name DESCRIPTION
The command adds the specified volume group to the system. The physical volumes, specified as pv_path ..., are scanned to obtain the vol- ume group information and logical volume information. This command works much like A user may explicitly create the vg_name directory and the file before importing the volume group. If absent, the command will automatically create the directory and the file, assigning the minor number as explained in the command man page (see vgcreate(1M)). The vg_name is added to the or file, and the associated logical volume device files are added to the system. assumes that the volume group information has already been created on the physical volumes. This command is useful in conjunction with the command (see vgexport(1M)), to move volume groups from one system to other systems within a high availability cluster. creates logical volume device files under the vg_name directory using the naming convention given in mapfile or using the default naming convention used by the command (see lvcreate(1M)). The command reconstructs the newly imported volume group entry in the or file. The order of the disks belonging to the newly imported vol- ume group could be different than it was before. When a bootable volume group is imported (volume groups version 1.0 only), the boot information present in the boot disks might be incor- rect due to the change in the order of disks in the file. This is because the boot information on the boot disks assumes a certain order of disks in and requires a resynchronization of this information after the first activation of a newly imported bootable volume group. To resynchronize the information on the boot disk after the first activation of a newly imported bootable volume group, run the command in recovery mode option). does not activate the imported volume group due to the many possible options at volume group activation time. To activate the volume group once it has been successfully imported, use the command (see vgchange(1M)). Options and Arguments recognizes the following options and arguments: pv_path The block device path names of a physical volume. This argument is not used with the and related options. vg_name The path name of the volume group. Specify the name of the file from which logical volume names and numbers are to be read. This option is optional when used as in the first com- mand line format of the If this option is not specified, logical volume names are created using the default naming convention where is the decimal representation of logical volume minor number. When used with the option, the volume group specified in the mapfile can be shared among the exporting system and the importing systems. Configure the volume group by populating persistent device special files in the or file, corresponding to the volume group, vg_name. (See intro(7) for information about device special files.) This option can only be used with option. If is invoked without a option, legacy device special files will be used to populate the or file. This option may become obsolete in future releases. Scan option. Scan each of the disks connected to the system and update the or file with the physical volumes that have matching volume group information, as found in the mapfile. This option should always be used in conjunction with the option. The specified mapfile is the file gener- ated by running the command, also with and options. Preview the actions to be taken but do not update the or file or add the logical volume device files. This option is best used in conjunction with the option. Print verbose messages including names of the logical volumes. Import the set of pv_paths held in the infile into the volume group. This option is used as an alternative to specifying the pv_paths on the command line. Each pv_path must appear on a new line in the infile. This option may not be used together with the option. WARNINGS
The option may become obsolete in future releases. No more than eight paths to any physical volume will be added to the or file. All other paths wll be omitted. The following warnings apply to the option, when importing disks with alternate paths: The command does not preserve the path ordering, when a volume group is exported and then imported. This may cause the primary and alter- nate paths to be different on an importing system, from that of an exported system. Also, additional alternate paths that were not config- ured on the exported system may get discovered and configured on the importing system. If the original primary path of a disk gets configured as an alternate path after the volume group is imported, the order can easily be reverted by using to remove the primary path and then reconfiguring the same path again as an alternate, using If additional alternate paths were added to the newly imported volume group, use to reduce any alternate paths that were added but not required. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Import the volume group that is located on physical disks and Activate the volume group following a successful import: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be used by the importing system only: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be shared among the exporting system, this system, and other systems importing the volume group as shared: Import the volume group using the infile, was previously specified by the command on another system, and it assumes that pv_paths in the are identical on both systems. SEE ALSO
vgexport(1M), vgscan(1M), intro(7), lvm(7). vgimport(1M)
All times are GMT -4. The time now is 12:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy