Sponsored Content
Full Discussion: creating luns vg
Operating Systems AIX creating luns vg Post 302186521 by itik on Thursday 17th of April 2008 12:19:55 PM
Old 04-17-2008
creating luns vg

Hi All,

I have these config on my old ssa.

Vg4 22GB (pps 256)
Vg2 88GB (pps 128)
Vg3 22GB (pps 256)
Vg8 88GB (pps 128)
Vg13 106GB (pps 32)
Vg12 106GB (pps 32)
Vg10 54GB (pps 64)
Vg11 54GB (pps 64)

When I create a lun on my san do I need to specify the same pps. If yes, how do I do that on my DS4300 SAN?

Thanks in advance,
itik
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

how can I monitoring the LUNs in HP storage

Hi, How can i monitoring the LUN in HP Storage with korn shells? I would like to have a shell can monitoring the LUN, VGs, lvols and raw devices. Jesus (3 Replies)
Discussion started by: jgutierrez29
3 Replies

2. HP-UX

HP LV's for Hitachin Luns

Hi, This is my first post and I hope I can present my questions the right way. I am going to be asked to create logical volumes for a Hitachi SAN device on a New HP 11 server. Currently, They are running their data on a EMC (prod server). They are looking to convert the data and filesystems over to... (3 Replies)
Discussion started by: Uni-dev
3 Replies

3. Filesystems, Disks and Memory

mount luns solaris

Hi Iīm new to san and lunīs I see the disks, but are not able to mount them bash-3.00# mountall checking ufs filesystems /dev/rdsk/c3t5006016930601F86d0s6: I/O error Can't open /dev/rdsk/c3t5006016930601F86d0s6: I/O error /dev/rdsk/c3t5006016930601F86d0s6: CAN'T CHECK FILE SYSTEM.... (1 Reply)
Discussion started by: ludvig
1 Replies

4. AIX

LUNS in AIX

Hi team, 2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR 2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR 2E493F13 0612155010 P H dac0 ARRAY OPERATION ERROR 2E493F13 0612154910 P H dac0 ARRAY OPERATION ERROR 2E493F13 0612154910 P H dac0 ... (4 Replies)
Discussion started by: kkeng808
4 Replies

5. HP-UX

Volume group are those LUNs?

In HP-UX, VLM: what volume group, are these LUNs? anyone know ? objecthexuid .........................: 6005-08b4-0001-529c-0005-6000-45d6-0000 objecthexuid .........................: 6005-08b4-0001-529c-0005-6000-45d9-0000 objecthexuid .........................:... (5 Replies)
Discussion started by: aav1307
5 Replies

6. Linux

Rescan LUNs on Linux VM

Hi, I have presented a new 70GB LUN to my RedHat Linux VM server. How do I rescan for the new LUN? Thanks, Sparcman:confused: (2 Replies)
Discussion started by: sparcman
2 Replies

7. Red Hat

Adding LUNs to system

Hi guys I have been asked for the following: SMI Oracle database PTP10 Oracle 10g RAC on usdfslprac4 and usdfslprac5 Linux boxes is reaching its space limit. It is just 20 GB away from being completely out of disk space. And then database will stop working and SMI system hence will be impacted.... (0 Replies)
Discussion started by: 300zxmuro
0 Replies

8. Solaris

luns

how to create luns plzzzzzz (1 Reply)
Discussion started by: nsusheelgoud
1 Replies

9. Red Hat

Scan For new LUNS

In Solaris the administrator has to update /kernel/drv/sd.conf file to tell the sd driver to scan for a broader range of scsi devices. Can someone please tell me what file needs to be update in Redhat Linux 5 for the same. Second part of the question is WWN for HBA's can be found (atleast in my... (1 Reply)
Discussion started by: Tirmazi
1 Replies

10. Solaris

SAN-based LUNs

running Solaris10 with Qlogic FC adapters connected to a multi-host FC array..using VXFS/VXVM.. Is there in Solaris10 or using some Qlogic drivers to filter out only the LUNs this host can see ?? Normally this is done by LUN masking in the FC switch or the FC array itself..however, neither... (2 Replies)
Discussion started by: ppchu99
2 Replies
csx_CS_DDI_Info(9F)					   Kernel Functions for Drivers 				       csx_CS_DDI_Info(9F)

NAME
csx_CS_DDI_Info - obtain DDI information SYNOPSIS
#include <sys/pccard.h> int32_t csx_CS_DDI_Info(cs_ddi_info_t *cdi); INTERFACE LEVEL
Solaris DDI Specific (Solaris DDI) PARAMETERS
cdi Pointer to a cs_ddi_info_t structure. DESCRIPTION
This function is a Solaris-specific extension that is used by clients that need to provide the xx_getinfo driver entry point (see get- info(9E)). It provides a method for clients to obtain DDI information based on their socket number and client driver name. STRUCTURE MEMBERS
The structure members of cs_ddi_info_t are: uint32_t Socket; /* socket number */ char* driver_name; /* unique driver name */ dev_info_t *dip; /* dip */ int32_t instance; /* instance */ The fields are defined as follows: Socket This field must be set to the physical socket number that the client is interested in getting information about. driver_name This field must be set to a string containing the name of the client driver to get information about. If csx_CS_DDI_Info() is used in a client's xx_getinfo function, then the client will typically extract the Socket value from the *arg argu- ment and it must set the driver_name field to the same string used with csx_RegisterClient(9F). If the driver_name is found on the Socket, the csx_CS_DDI_Info() function returns both the dev_info pointer and the instance fields for the requested driver instance. RETURN VALUES
CS_SUCCESS Successful operation. CS_BAD_SOCKET Client not found on Socket. CS_UNSUPPORTED_FUNCTION No PCMCIA hardware installed. CONTEXT
This function may be called from user or kernel context. EXAMPLES
Example 1: : Using csx_CS_DDI_Info The following example shows how a client might call the csx_CS_DDI_Info() in the client's xx_getinfo function to return the dip or the instance number: static int pcepp_getinfo(dev_info_t *dip, ddi_info_cmd_t cmd, void *arg, void **result) { int error = DDI_SUCCESS; pcepp_state_t *pps; cs_ddi_info_t cs_ddi_info; switch (cmd) { case DDI_INFO_DEVT2DEVINFO: cs_ddi_info.Socket = getminor((dev_t)arg) & 0x3f; cs_ddi_info.driver_name = pcepp_name; if (csx_CS_DDI_Info(&cs_ddi_info) != CS_SUCCESS) return (DDI_FAILURE); if (!(pps = ddi_get_soft_state(pcepp_soft_state_p, cs_ddi_info.instance))) { *result = NULL; } else { *result = pps->dip; } break; case DDI_INFO_DEVT2INSTANCE: cs_ddi_info.Socket = getminor((dev_t)arg) & 0x3f; cs_ddi_info.driver_name = pcepp_name; if (csx_CS_DDI_Info(&cs_ddi_info) != CS_SUCCESS) return (DDI_FAILURE); *result = (void *)cs_ddi_info.instance; break; default: error = DDI_FAILURE; break; } return (error); } SEE ALSO
getinfo(9E), csx_RegisterClient(9F), ddi_get_instance(9F) PC Card 95 Standard, PCMCIA/JEIDA SunOS 5.10 19 Jul 1996 csx_CS_DDI_Info(9F)
All times are GMT -4. The time now is 11:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy