Sponsored Content
Operating Systems Solaris Can't remove a LUN from a Zpool! Post 302391462 by BG_JrAdmin on Monday 1st of February 2010 11:50:55 AM
Old 02-01-2010
Can't remove a LUN from a Zpool!

I am not seeing anyway to remove a LUN from a Zpool...

Am I missing something? or do i have to destroy the zpool and recreate it?
 

10 More Discussions You Might Find Interesting

1. Solaris

Remove the exported zpool

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

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

3. Solaris

ZPOOL help..

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

4. UNIX for Advanced & Expert Users

How to remove the LUN in RHEL?

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

5. Solaris

Bad exchange descriptor : not able to remove files under zpool

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

6. Solaris

Lun remove, stuck in /dev/dsk and /dev/rdsk

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

7. Solaris

Cannot remove disk added to zpool

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

8. Solaris

Restore of Netapp FC lun targets used as the disks for a zpool with exported zfs file systems

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

9. Solaris

How to remove a LUN in "Online Busy" state?

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

10. Solaris

Zpool mirroring

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
TARG(4) 						   BSD Kernel Interfaces Manual 						   TARG(4)

NAME
targ -- SCSI target emulator driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device targ DESCRIPTION
The targ driver provides an interface for usermode programs to emulate SCSI target devices. A sample program that emulates a disk drive (similar to da(4)) can be found in /usr/share/examples/scsi_target. The targ driver supplies the control device /dev/targ. After opening the device, the file descriptor must be bound to a specific bus/tar- get/LUN and enabled to process CCBs using the TARGIOCENABLE ioctl. The process then uses write(2) to send CCBs to the SIM and poll(2) or kqueue(2) to see if responses are ready. Pointers to completed CCBs are returned via read(2). Any data transfers requested by the user CCBs are done via zero-copy IO. IOCTLS
The following ioctl(2) calls are defined in the header file <cam/scsi/scsi_targetio.h>. TARGIOCENABLE (struct ioc_enable_lun) Enable target mode on the LUN specified by the following structure: struct ioc_enable_lun { path_id_t path_id; target_id_t target_id; lun_id_t lun_id; int grp6_len; int grp7_len; }; The selected path (bus), target, and LUN must not already be in use or EADDRINUSE is returned. If grp6_len or grp7_len are non-zero, reception of vendor-specific commands is enabled. TARGIOCDISABLE Disable target mode and abort all pending CCBs. The CCBs may optionally be read as they complete. TARGIOCENABLE can then be called to activate a different LUN. Multiple disable calls have no effect. The close(2) system call automatically disables target mode if enabled. TARGIOCDEBUG (int) Enables CAM_PERIPH debugging if the argument is non-zero, otherwise disables it. FILES
<cam/scsi/scsi_targetio.h> describes the usermode interface. /sys/cam/scsi/scsi_target.c is the driver source file. /dev/targ is the control device. SEE ALSO
/usr/share/examples/scsi_target, ahc(4), isp(4), scsi(4) FreeBSD Target Information, http://www.root.org/~nate/freebsd/. AUTHORS
The targ driver first appeared in FreeBSD 3.0 and was written by Justin T. Gibbs. It was rewritten for FreeBSD 5.0 by Nate Lawson <nate@root.org>. BUGS
Currently, only the ahc(4) and isp(4) drivers fully support target mode. The ahc(4) driver does not support tagged queuing in target mode. BSD
December 13, 2011 BSD
All times are GMT -4. The time now is 03:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy