Just thinking - you shouldn't have to boot to maintenance mode to do this, just need to make sure after the rename that the root flag is on the one you want to keep before you offline and destroy the other. But since both volumes are offline in your example you must already be in maintenance mode...
Regards,
Alan McLachlan Technical Analyst Information Management Services Department of Education, Training and the Arts (DETA) Floor 11 Education House, 30 Mary Street, Brisbane Fax: 07 3237 9695 Mob: 0429 655644
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of MCLACHLAN, Alan Sent: Friday, May 11, 2007 9:39 AM To: Michael Homa Cc: toasters@mathworks.com Subject: RE: Duplicate nonboot vol0
Try booting to maintenance mode and do a vol rename - you should find only one of the "vol0" volumes is renamed. Then identify which volume is the real one and destroy the other. If the one that was renamed was the real vol0 you can rename it back to vol0 if you wish (root volume doesn't have to be called "vol0").
Regards,
Alan McLachlan Technical Analyst Information Management Services Department of Education, Training and the Arts (DETA) Floor 11 Education House, 30 Mary Street, Brisbane Fax: 07 3237 9695 Mob: 0429 655644
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Michael Homa Sent: Friday, May 11, 2007 8:59 AM To: toasters@mathworks.com Subject: Duplicate nonboot vol0
We have a backup F740, running 6.4.5, that serves as an insurance to our production, primary, netapp system. And, yes, before someone suggests it, we are in the process of upgrading it to a 270 with a more recent version of ONTAP.
Somehow a second vol0 (obviously traditional since the ONTAP < 7) was created and I'm trying to figure out how to destroy it:
Volume State Status Options vol0 offline normal raidsize=14
Plex /vol0/plex0: online, normal, active RAID group /vol0/plex0/rg0: normal RAID group /vol0/plex0/rg1: normal
vol0 offline normal raidsize=14
Plex /vol0/plex0: online, normal, active RAID group /vol0/plex0/rg0: normal RAID group /vol0/plex0/rg1: normal
A disk in the duplicate vol0 is bad and that's how I discovered the problem:
Volume vol0 (restricted, normal) (block checksums) Plex /vol0/plex0 (online, normal, active) RAID group /vol0/plex0/rg0 (degraded)
RAID Disk Device HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ------ --------------- ---- -------------- -------------- parity 7.48 7 3 0 FC:A 68000/139264000 69536/142410400 data FAILED N/A 68000/139264000
I'm a bit unsure how to proceed. If I pull the disk, will the system not grab one of the spares and rebuild on it? What I'd like to happen is have the system rename the bad vol0 as vol0(1) and then I can use the vol destroy command to get rid of it. How do I do that? If I use the vol rename command, there's the issue of identifying the "bad" vol0 and not the one I want to retain.
There was a ticket in the netapp knowledge base with a procedure but that situation was for a duplicate boot vol0s
I'm sure this is relatively simple yet I haven't come up with a solution.
Michael Homa Operating Systems Support and Database Group Academic Computing and Communication Center University of Illinois at Chicago email: mhoma@uic.edu