10 More Discussions You Might Find Interesting
1. Solaris
Now this doesnt look right to me. All of these disks are 100Gb LUNS so total zpool size is 300Gb.
Am I right in saying that this zpool consists of two disks plus one more disk that is 6 way mirrored?
So a bit pointless because only one of the three is mirrored (and 6 way is a bit of overkill... (3 Replies)
Discussion started by: psychocandy
3 Replies
2. Solaris
Hi all, I have a LUN that is in "Online Busy" when I issue the dev_gestate subcommand of luxadm:
root@es088wb6:~# luxadm -v -e dev_getstate /dev/rdsk/c21t50050763090887FEd4s2
phys path = "/devices/pci@6c0/pci@1/pci@0/pci@4/SUNW,qlc@0/fp@0,0/ssd@w50050763090887fe,4:c,raw"
... (5 Replies)
Discussion started by: ludiegu
5 Replies
3. Solaris
So,
We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup
FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies
4. Solaris
I added a disk to a zpool using "zpool add diskname"
My intention was mirror a zpool disk that no mirror; that is a zpool with only one disk. I did not issue the right command. Now, the disk has been added successfully but I cannot remove nor detach it as Solaris 11 thinks it has data on it... (14 Replies)
Discussion started by: LittleLebowski
14 Replies
5. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
6. Solaris
Hi ,
One of my zone went down and when i booted it up i could see the pool in degraded state with some check sum errors . we have brought the pool online after scrubbing. But few files are showing this error
Bad exchange descriptor
Please let me know how to remove these files (2 Replies)
Discussion started by: chidori
2 Replies
7. UNIX for Advanced & Expert Users
Hi,
How to remove the allocate SAN Lun on the Linux Server. I am using rhel 5.8. I have assigned a LUN to the existing Volume group.
For eg: I have allocated a LUN with 20GB to the existing volume group(test123). Now, how can I take back the allocated lun without any issues. (1 Reply)
Discussion started by: gsiva
1 Replies
8. Solaris
hi ...
i have added a physical disk to the pool with
""zpool add <poolname> diskname"""... after that i realized that i have to mirror it instead..then i tried to take that disk out of the pool but i m not able to do that..
i have gone through many unix help sites , nothing worked ,
so please... (6 Replies)
Discussion started by: yrajendergoud
6 Replies
9. Solaris
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
10. Solaris
I had a pool which was exported and due to some issues on my SAN i was never able to import it again. Can anyone tell me how can i destroy the exported pool to free up the LUN. I tried to create a new pool on the same pool but it gives me following error
# zpool create emcpool4 emcpower0c... (0 Replies)
Discussion started by: fugitive
0 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)
