I have had this occur a couple of times over the years. Note in Michael's case the two vol0's were on the same physical disks, so it wasn't a result of drive adds. If you search on NOW I think from memery there's a bug article in about a race condition where this can occur. I'm too busy to bother looking it up right now ;)
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 Dave Rubright Sent: Friday, May 11, 2007 10:41 AM To: Michael Homa; toasters@mathworks.com Subject: RE: Duplicate nonboot vol0
I'm curious as to how you ended up with 2 volumes called vol0. Meaning, you can't create a volume named vol0 if it already exists even if it's offline. My only guess would be that you added some drives that were part of another 2 disk volume called vol0 which ONTAP should have renamed to vol0(1) when inserted. Not sure what happened there but...
So an option if you did add drives, you should know which drives you added and remove them. If you don't know which drives were added then a prior autosupport should tell you which drives were dedicated to the original vol0 and remove the ones not on the volume list.
From here you should be able to rename original vol0 to another name (orig_vol) and bring online. Pop in the drives you removed and offline vol0, destroy it. Then you can rename "orig_vol" volume back to vol0.
Dave Rubright Jr 4Base Technology, Inc
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Michael Homa Sent: Thursday, May 10, 2007 3:59 PM 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: normalA 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/13926400069536/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