Sponsored Content
Full Discussion: Mounting LUN on HP 11.31
Operating Systems HP-UX Mounting LUN on HP 11.31 Post 302528109 by letters on Monday 6th of June 2011 12:16:04 PM
Old 06-06-2011
Re-Hello,

I have another problem : i want to mount the same Lun on 2 different servers and at the end I have 2 different mounted points !
 

10 More Discussions You Might Find Interesting

1. 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

2. UNIX for Dummies Questions & Answers

LUN mapping

Hi, We recently purchased a 3 tb RAID. In the setup, it created 2 slices, one 2 tb and one 1 tb slice. Right now only the 2 tb slice is visible when booting up. I was told that the second slice needs to be mapped to a lun and a port like the first slice is. Does anyone know how I would go... (1 Reply)
Discussion started by: user23
1 Replies

3. Solaris

LUN not ready

hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies

4. 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

5. AIX

Expand LUN

Hello all, I have the following env: * DS4300 storage SAN * AIX 5.3 Lpar (storage through vio server) * AIX 5.3 Server Some FS are too small do I'm setting up a process to increase the size of the FS. To expand the size of the FS I plan to do the following for the physical AIX server,... (1 Reply)
Discussion started by: petervg
1 Replies

6. AIX

LUN Behavior

Aix 6.1, working with a nim master and nim_altmaster both LPARS have access to the same data LUN, /nimdisk I do realize the risks of having 2 servers access the same LUN, however it serves the purpose of being able to restore mksysb's to/from our DR site if necessary, at least in theory ;) ... (3 Replies)
Discussion started by: mshilling
3 Replies

7. Red Hat

How to configure LUN

Hi ALL, what are the steps to detect and configure a new attached lun in RHEL 5.3. rgds, snj. (2 Replies)
Discussion started by: snjksh
2 Replies

8. Red Hat

Detect the lun

Hi, Is there command to detect the newly added LUN is linux box. I tried with below commands, but that doesn't work out. fdisk -l, fdisk -l | grep Disk pvscan (5 Replies)
Discussion started by: gsiva
5 Replies

9. Emergency UNIX and Linux Support

Reuse a LUN

I have a LUN (From HP-Storage VA7110) that is claimed on 2 servers, but is in used in one of the VG on Server-1 . Now I want to shut Server-1 and re-use that LUN on server-2 . Server-1 Path-1 : /dev/rdsk/c4t0d1 Path-2: /dev/rdsk/c6t0d1 Server-2 Path-1: /dev/rdsk/c5t0d1 Path-2:... (8 Replies)
Discussion started by: Shirishlnx
8 Replies

10. AIX

Not getting Lun Id

Hi, I am not getiting lun id information on VIO Server. I have used the command fget_config command. just showing # prompt. I would like know wheather any other command is there equiv of fget_config which will display lun id? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
iobind(1M)																iobind(1M)

NAME
iobind - bind a driver to a device SYNOPSIS
instance] DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it. As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware paths. The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The optional forces the binding to occur at the next reboot if it cannot be done online. The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The user is given the option to proceed or not. If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown by the command: The specified driver was successfully bound to the hardware path. The specified driver cannot be used to claim the hardware at the specified hardware path. The device at the address is responding, but it is in an error state. The device at the specified hardware path is no longer responding. The specified hardware path is locked. Try again later. The driver failed. Options recognizes the following options: Force the binding even though a driver does not support online unbinding and binding or the device is in use. In this case, the binding will take effect at the next reboot. The LUN hardware path of a device must be of the form 64000/0x/0x. The instance number to be assigned to the device. The name of the driver that the LUN and legacy hardware paths are to be bound to. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class. Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot. WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If this happens, must be executed again to bind the desired driver. may be executed only by the superuser. SEE ALSO
ioscan(1M), intro(7). iobind(1M)
All times are GMT -4. The time now is 03:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy