UNSOLVED

jroczniak

updated

14 years ago

J

jroczniak

1 Rookie

30 Posts

0

4091

August 2nd, 2012 05:00

Cannot delete LUNs

I have encountered an issue on a 480 that I cannot fix. I am trying to delete 29 LUNs but the system will not let me, I get the pop up warning window that says the LUN is being used by something else such as a snap, mirror, RLP, etc, etc... as far as I can tell none of that is true. There are no storage groups on the system, no snaps, no clones, etc. etc. Below I have some CLI outputs for LUN 19, all the others have the same results....

Navisphere CLI>naviseccli -h x.x.x.x -user nasadmin -password nasadmin -scope 0 getagent

Agent Rev:           7.30.15 (0.44)
Name:                K10
Desc:
Node:                A-APM00104302383
Physical Node:       K10
Signature:           2781304
Peer Signature:      2773447
Revision:            04.30.000.5.524
SCSI Id:             0
Model:               CX4-480
Model Type:          Rackmount
Prom Rev:            5.30.00
SP Memory:           8160
Serial No:           APM00104302383
SP Identifier:       A
Cabinet:             SPE5

naviseccli -h x.x.x.x -user nasadmin -password nasadmin -scope 0 getlun -messner 19 -stack

Listed Driver:             K10RollBackAdmin

                            K10FarAdmin

                            K10SnapCopyAdmin

Navisphere CLI>naviseccli -h x.x.x.x -user nasadmin -password nasadmin -scope 0  mirror -async -setfeature -off -lun 19

Async mirror: Removing driver from lu stack failed.  This LUN is already allocated to a storage group. Check that this is the correct LUN, and if so, remove the LUN from the storage group and try again. (0x79008023)

Navisphere CLI>naviseccli -h x.x.x.x -user nasadmin -password nasadmin -scope 0  mirror -async -setfeature -off -lun 6

Async mirror: Removing driver from lu stack failed.   The shadow LU that we were attempting destroy was associated with a mirror.  Remove the mirror before attempting this operation.  (0x71528274)

As I stated above there are no storage groups or mirrors that I can see, this might be the result of a badly backed out mirrorview migration in the past.

Any ideas?

Thanks!