Sponsored Content
Full Discussion: Volume Groups and the SAN
Operating Systems AIX Volume Groups and the SAN Post 302174219 by mhenryj on Monday 10th of March 2008 11:52:30 AM
Old 03-10-2008
Volume Groups and the SAN

Hello all. I have a perplexing problem

I have an AIX 5.1 system on an EMC SAN.

This system had been on a CX400 SAN for several years. The system was migrated to a CX700 just over a week ago. The migration consisted of utilizing on of the HBAs in the system and connecting to both SANs

The VGs were expaned and mirrored. Then the VGs were reduced and the old SAN removed. Then both HBA being connected to the new CX700.

Since the migration, when the system is booted, the VGs on the SAN do not come up active (this has happened twice), and, of course, the file systems don't mount.

I can export the VGs, import them, fix the /etc/filesystems file and then mount all of the FSs, but this is a pain.

The VGs are set to auto mount

Any insight into what might be happening is appreciated.

Thanks
Mike
 

10 More Discussions You Might Find Interesting

1. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

2. Linux

Howto clone/migrate a volume in the SAN

Dear Srs, I have a Linux server (linux01) booting from SAN with a volume in a Nexsan SATAbeast storage array (san01). The disk/volume has four ext3 partitions, total size is near to 400GB, but only 20-30GB are in use. I need to move this disk/volume to another Nexsan SATAbeast storage array... (0 Replies)
Discussion started by: Santi
0 Replies

3. Red Hat

how to mount SAN volume with its increased size

Hi, We have 200GB SAN volume mounted on Redhat EL 5. which is working fine. As my SAN supports dynamic resizing of volumes, i unmounted the volume and resized the SAN Volume to 300 GB successfully. Then i mounted again but it shows 200GB only but data is intact. Now, my requirement is to let... (3 Replies)
Discussion started by: prvnrk
3 Replies

4. Solaris

Ldom OS on SAN based zfs volume

Is it possible to use zvol from SAN LUN to install LDOM OS ? I 'm using following VDS from my service domain VDS NAME LDOM VOLUME DEVICE primary-vds0 primary iso sol-10-u6-ga1-sparc-dvd.iso cdrom ... (16 Replies)
Discussion started by: fugitive
16 Replies

5. UNIX for Advanced & Expert Users

volume groups

Do we have concepts of volume groups in solaris like we have in Linux(command: vgdiplay) and AIX(command: lsvg). If yes, then what commands/ files can give details for same. (1 Reply)
Discussion started by: epriya2003
1 Replies

6. Solaris

Volume groups

Do we have concepts of volume groups in solaris like we have in Linux(command: vgdiplay) and AIX(command: lsvg). If yes, then what commands/ files can give details for same. (5 Replies)
Discussion started by: epriya2003
5 Replies

7. AIX

hdisk status in sdd volume groups

hi all we recently upgraded our san switches. after that, i found i got many hdisks showing in lsdev with status "Defined" and "Available". the number of "Defined" is equal to "Available". the time stamp shows all "Available" disks created at our downtime night. "datapath query device"... (0 Replies)
Discussion started by: rs6000er
0 Replies

8. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

9. Red Hat

Volume group not activated at boot after SAN migration

I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
st_ats_enabled(5)						     OBSOLETED							 st_ats_enabled(5)

NAME
st_ats_enabled - determine whether to reserve a tape device on open (OBSOLETED) VALUES
Default Allowed values or Recommended values DESCRIPTION
Note: this tunable is obsoleted and has been renamed to beginning with release HP-UX 11i v3. This tunable notifies the stape or estape driver whether it needs to reserve a tape device on open and subsequently release it on close. When this tunable is on the stape or estape driver will attempt to reserve any tape device on open. The driver has a few tape devices flagged as suitable devices for this functionality including DLT 8000, DLT 7000, STK 9840, HP Ultrium, and others. DDS drives are not flagged for this functionality. The tunable allows the safe sharing of tape devices in multinode configurations like MC/ServiceGuard's Advanced Tape Sharing. The auto- matic reserve and release protects the tape device from being accessed from multiple nodes which would corrupt a backup. If the reserve portion of the stape or estape driver's open routine fails, a status of is returned. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately and are used during the next open or close. When Should the Tunable Be Turned On? This tunable should be turned on if the system will be used in an MC/ServiceGuard Advanced Tape Sharing configuration or the user wants the stape or estape driver to use automatic reserve or release on open and close for multinode manageability. What Are the Side Effects of Turning the Tunable On? A reserve is sent to the tape device by the stape or estape driver on open and a release is sent on close. No other initiator or HBA will be able to access the tape device while it is opened on another initiator or HBA. When Should the Tunable Be Turned Off? This tunable should be turned off for any SAN tape sharing solution configuration other than ATS. Most multinode backup applications (for example, Omniback) manage device reservation themselves and any interference by the stape or estape driver may produce problems. This tun- able should also be turned off for any multiplatform SAN configuration to keep tape access across platforms more uniform. What Are the Side Effects of Turning the Tunable Off? Unauthorized access from another initiator might interfere with any current tape operation. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
st_ats_enable(5), scsi_tape(7), scsimgr_estape(7). Tunable Kernel Parameters st_ats_enabled(5)
All times are GMT -4. The time now is 06:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy