Hi everybody,
I came across a strange problem today, and all the well-meaning people on google and netapp community could not provide an answer as far as I could see.
Nutshell: New environment, first v-series, fabric metro cluster.
After assigning the disks wrongly the first time (missing -p <pool>) I’ve tried "disk assign <disk_id> -o unowned ” without luck, I did a "disk remove_ownership”.
It worked, sort of.
There is one LUN left, which both controllers claim that the other controller own. Since the controllers can’t unown luns they don’t own, I am finding myself in a bit of a pickle.
Has anyone come across this situation before?
disk show -v to show the sysid of the system that owns it.
priv set advanced disk reassign -s <old sysid> -d <new sysid> priv set
Duncan Cummings NetApp Specialist Interactive Pty Ltd Telephone 07 3323 0800 Facsimile 07 3323 0899 Mobile 0403 383 050 www.interactive.com.au
------Confidentiality & Legal Privilege------------- "This email is intended for the named recipient only. The information contained in this message may be confidential, or commercially sensitive. If you are not the intended recipient you must not reproduce or distribute any part of the email, disclose its contents to any other party, or take any action in reliance on it. If you have received this email in error, please contact the sender immediately. Please delete this message from your computer. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you."
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Svein Harang Sent: Wednesday, 18 June 2014 8:14 AM To: Toasters@teaparty.net Subject: v-series lun ownership
Hi everybody,
I came across a strange problem today, and all the well-meaning people on google and netapp community could not provide an answer as far as I could see.
Nutshell: New environment, first v-series, fabric metro cluster.
After assigning the disks wrongly the first time (missing -p <pool>) I’ve tried "disk assign <disk_id> -o unowned ” without luck, I did a "disk remove_ownership”.
It worked, sort of.
There is one LUN left, which both controllers claim that the other controller own. Since the controllers can’t unown luns they don’t own, I am finding myself in a bit of a pickle.
Has anyone come across this situation before?
-- Sincerely / Mvh Svein Harang sh@basefarm.com +47 4000 4200 Direct: +47 417 36 019
I came across a strange problem today, and all the well-meaning people on google and netapp community could not provide an answer as far as I could see.
Nutshell: New environment, first v-series, fabric metro cluster.
After assigning the disks wrongly the first time (missing -p <pool>) I’ve tried "disk assign <disk_id> -o unowned ” without luck, I did a "disk remove_ownership”.
It's "disk assign -s unowned". "-s", not "-o". -o sets owner name, not sure what effect it has in this case (should have failed due to unknown name I presume).
It worked, sort of.
There is one LUN left, which both controllers claim that the other controller own. Since the controllers can’t unown luns they don’t own, I am finding myself in a bit of a pickle.
Please paste exact commands and their output you used to verify it.
-
Borzenkov, Andrei -
Duncan Cummings -
Svein Harang