Hi guys,
We're running DataOnTap 5.2.1 on a bunch of F330s. One of them had a disk failure this weekend, and since I was in for a power shutdown, I figured I'd just swap in a spare disk from a returned filer (upgrade to an F740).
The problem is the before the old F330 was returned, we never did any of the disk commands to make all the disks into spares. We just copied the data off and shutdown the system.
So I took one of these disks from the old Filer and did the usual disk swap, disk swap procedure to put it into the Filer with the failed disk. And now comes the problem. The Filer sees the new disk and scans it in, but hey! It's got volume info on it, and it won't initialize the disk and just use it on the new filer.
Sigh... I've tried using the command 'disk fail 8a.4' but it won't let me because it's part of a volume.
So I look at the volume status and I get this:
swtoast> vol status Volume State Status Options vol0 online normal root vol0 offline foreign partial
Yup, *two* volumes, both named 'vol0' and I can't get rid of the foreign one. If I just do 'vol status vol0' I get the online volume listed. What I want to do is just a volume destroy, or a disk initialize without any questions asked. But I can't figure out how to do this.
Any hints? I do have a call into NetApp, but I've been on hold for about 15 minutes already...
Thanks, John John Stoffel - Senior Unix Systems Administrator - Lucent Technologies stoffel@lucent.com - http://www.lucent.com - 978-952-7548 john.stoffel@ascend.com - http://www.ascend.com
"John" == John Stoffel john@casc.com writes:
John> Yup, *two* volumes, both named 'vol0' and I can't get rid of John> the foreign one. If I just do 'vol status vol0' I get the John> online volume listed. What I want to do is just a volume John> destroy, or a disk initialize without any questions asked. John> But I can't figure out how to do this.
John> Any hints? I do have a call into NetApp, but I've been on John> hold for about 15 minutes already...
Floppy boot, rc_toggle_basic, disk_erase_label.
j. -- Jay Soffian jay@cimedia.com UNIX Systems Engineer 404.572.1941 Cox Interactive Media
Thanks guys, I've gotten alot of responces from various places, as well as from NetApp tech support.
Basically, I need to do:
filer> rc_toggle_basic
Now notice the * in the prompt, it means we're in super duper mode. Now we clean the disk header:
filer*> disk_erase_label <disk>
Which does what I need. I then did a rc_toggle_basic again to get back to normal mode, then I did a double disk swap to remove and re-insert the problem disk.
It came back properly as a spare disk.
There are still two issues with DataOnTap 5.2.1 though:
1. It allows two different volumes with the same name to exist on the system.
2. When you remove the last disk in a volume, it keeps the volume around. I think this is somewhat related to #1 though.
John John Stoffel - Senior Unix Systems Administrator - Lucent Technologies stoffel@lucent.com - http://www.lucent.com - 978-952-7548 john.stoffel@ascend.com - http://www.ascend.com
On Mon, 4 Oct 1999, John Stoffel wrote:
There are still two issues with DataOnTap 5.2.1 though:
- It allows two different volumes with the same name to exist on the system.
I had a similar situation just yesterday. I have four new filers (with 5.2.3 installed), each with a single disk shelf. Being adventurous, I hook all four shelves to a single filer. It boots up and makes all sorts of noise about mismatched NVRAM serial numbers and having to deal with *four* volumes, all named vol0, and all trying to be root volumes.
I forget what I did exactly, but disk_erase_label was in there, as well as renaming the real vol0 volume to something else, "exposing" the other vol0's underneath. I could then "vol offline" and "vol destroy" the foreign drives.
So I look at the volume status and I get this:
swtoast> vol status Volume State Status Options vol0 online normal root vol0 offline foreign partial
Hmm. At least in 5.0, it would, at least in some situations, prepend a "subscript" of the form "(1)" to the names of foreign volumes that would otherwise have a name identical to a native volume, so that you *could* delete or rename such a volume.
I'll have to check to see what happened to that....
-
Brian Tao -
Guy Harris -
Jay Soffian -
John Stoffel