This post is more than 5 years old
124 Posts
0
4559
January 6th, 2011 07:00
Forcing iSCSI LUN deletion on Celerra
We have a Celerra NX4, with new Unisphere, Dart 6 installed. There are a few iSCSI LUNs on the Celerra that are no longer being used by any iSCSI clients, to the best of my knowledge. LUN masks have been removed from them, etc.
However, I can't delete them. DART insists that they are still in use.
What diagnostics can I run to determine what servers are still logged in and mapping those iSCSI volumes? And, how can I force the Celerra to delete them if they are in fact not being used?
Thanks,
Eric
No Events found!
Rainer_EMC
4 Operator
•
8.6K Posts
0
January 10th, 2011 10:00
Force is good – but it wont work if these snaps are still promoted
Rainer_EMC
4 Operator
•
8.6K Posts
1
January 6th, 2011 07:00
Check if they still have checkpoints (snapshots)
If not – please open a service request
dynamox
9 Legend
•
20.4K Posts
0
January 6th, 2011 07:00
are they replicated ?
emarzock1
124 Posts
0
January 6th, 2011 07:00
Thanks for the quick reply, Rainer.
Yes, I checked the checkpoints also. None that I found. I actually think that this may be the issue, and that there are some snaps that are somehow hidden from my view.
d.engamba
16 Posts
0
January 6th, 2011 08:00
Hi,
are they in a clone group?
dynamox
9 Legend
•
20.4K Posts
0
January 6th, 2011 08:00
clone group ? Celerra iSCSI LUNs ?
emarzock1
124 Posts
0
January 6th, 2011 08:00
Thanks for the inquiry.
No, they are not replicated.
chrisimes
24 Posts
1
January 6th, 2011 18:00
Even if you aren't using Replication Manager, have a look at the following article:
If you are (or were) using Replication Manager, versions prior to v5.2.4 and v5.3.0 would under certain circumstances leave behind some "phantom" snaps which, of course, eventually started taking up space on the filesystem and had to be manually identified and then cleaned up. Even if you aren't running Replication Manager, it is still worth following the few steps to see if these are preventing you from deleting the iSCSI LUNs cleanly.
FYI, in Replication Manager v5.3.0 (and also in v5.2.4), dev had rolled in some hotfixes after identifying the (known) conditions causing this.
emarzock1
124 Posts
0
January 7th, 2011 07:00
Christopher,
Thanks for this answer. I will take a look, and let you know if this is the issue. It is plausible, since RM is part of our environment here.
Thanks,
Eric
dynamox
9 Legend
•
20.4K Posts
0
January 10th, 2011 09:00
can you su to root and try again ( su ..not su - )
emarzock1
124 Posts
0
January 10th, 2011 09:00
Sure enough, there are snaps all over the iSCSI volumes, but aren't showing up in the GUI.
My next challenge appears to be running the iscsi snap delete command...
[nasadmin@celerracs ~]$ server_iscsi server_2 -snap -delete fs83_T6_LUN6_SL7E9083700089_0000.ckpt007
server_2 :
Error 13159038990: Operation is not authorized.
Any help here???
Thanks,
Eric
emarzock1
124 Posts
0
January 10th, 2011 10:00
Yes, I tried rebooting.
There is a primus article on the error that I received. I will look into that. EMC223296
Rainer_EMC
4 Operator
•
8.6K Posts
0
January 10th, 2011 10:00
I assume you tried rebooting data mover ?
emarzock1
124 Posts
0
January 10th, 2011 10:00
A-HA! There is a -Force option...
[root@celerracs nasadmin]# server_iscsi server_2 -snap -delete fs51_T6_LUN202_SL7E9083700089_0000.ckpt000 -Force
server_2 :
OK
I'm on my way!
emarzock1
124 Posts
0
January 10th, 2011 10:00
By the way, these snaps were apparently created with RM...
[root@celerracs nasadmin]# server_iscsi server_2 -snap -info fs51_T6_LUN202_SL7E9083700089_0000.ckpt000
server_2 :
Snap Name = fs51_T6_LUN202_SL7E9083700089_0000.ckpt000
Lun Number = 202
Target = nx4-iscsi-target
Promoted Number =
Promoted Initiator =
Application Label = R.e.p.l.i.c.a.t.i.o.n. .M.a.n.a.g.e.r
LUN Size MB = 50000
Create Time = Fri Aug 28 16:24:17 EDT 2009
Application Data = (non-printable characters)