ONTAP Discussions

Disk assign in a MetroCluster, I have an external LUN in another dimension

c_morrall
3,682 Views

I have a V-series MetroCluster with external storage arrays. Something has gone missing for one external LUN (LDEV from a USP-V/XP24000 in my case). I've used &quot;disk assign -s unowned, disk assign -o <filer>&quot; successfully for other external LUNs, but not this one.

DSA002DC01> disk show NFC002DC04:1-1.126L11 

DISK      OWNER                      POOL  SERIAL NUMBER        HOME

------------ -------------              -----  -------------        -------------

NFC002DC04:1-1.126L11 DSA002DC02(151753476)    Pool0  50 134650102          DSA002DC02(151753476)

DSA002DC01> disk assign NFC002DC04:1-1.126L11 -s unowned

disk assign: Disk is currently owned by the partner and cannot be assigned.

Lets try it on the partner node then:

DSA002DC02> disk assign NFC002DC04:1-1.126L11 -s unowned

disk assign: Disk is currently owned by the partner and cannot be assigned.

DSA002DC02> disk show NFC002DC04:1-1.126L11  

DISK      OWNER                      POOL  SERIAL NUMBER        HOME

------------ -------------              -----  -------------        -------------

NFC002DC04:1-1.126L11 DSA002DC01(151751417)    FAILED 50 134650102          DSA002DC01(151751417)

DSA002DC02>

I may not have the full picture here, but it looks to me like both nodes in the MetroCluster thinks the partner owns the disk and I can't assign it to the filer where I want it.

1 ACCEPTED SOLUTION

c_morrall
3,682 Views

This was in the end solved by unpresenting the external LUN from the third party array, and then presenting it again.

View solution in original post

4 REPLIES 4

radek_kubka
3,682 Views

Hi,

Have you tried the same command, but with the -f option to force the operation?

Regards,
Radek

aborzenkov
3,682 Views

Hmm ... I'd find out first why it is shown as FAILED on one head ...

stuartwatkins
3,682 Views

Not really my specialist subject but if the disk is showing as already assigned you will need to unassign it from one of them.  You will have to do a priv set advanced to see the option, which is

disk remove_ownership <disk name>

Hope that helps

c_morrall
3,683 Views

This was in the end solved by unpresenting the external LUN from the third party array, and then presenting it again.

Public