Hi,
I have a filer with two volumes, and I'd like to remove the first volume and keep the second one only.
Is it as easy as doing: - copy of /etc from the first one to the second one - remove the firt volume - boot on floppy - download - reboot. ?
Also, not that I have any reason to do that, but if I wanted to put the first volume back, how does the filer know which volume to boot on?
Marc
Hi Marc,
At the risk of sounding official...
I have a filer with two volumes, and I'd like to remove the first volume and keep the second one only.
Is it as easy as doing:
- copy of /etc from the first one to the second one
- remove the firt volume
- boot on floppy
- download
- reboot.
?
Also, not that I have any reason to do that, but if I wanted to put the first volume back, how does the filer know which volume to boot on?
download affects all the disks, so you won't need to redownload the kernel (unless, of course, you're upgrading the kernel at the same time). However, you need to inform the filer of where the /etc files are located, so you'll need to do a "vol options <foo> root" before booting.
Thus: - copy /etc from <bar> to <foo> - "vol options <foo> root" - shut down - remove <bar> - boot
and that should do it.
Marc
Steve Member of Technical Staff Network Appliance, Inc.
On Wed, Jul 29, 1998 at 03:47:48PM -0700, Steve Rodrigues wrote:
At the risk of sounding official...
Not at all :-)
download affects all the disks, so you won't need to redownload the kernel (unless, of course, you're upgrading the kernel at the same time).
Ok (I didn't know if download would only download on the root volume or all of them).
However, you need to inform the filer of where the /etc files are located, so you'll need to do a "vol options <foo> root" before booting.
Ah! That's the command I didn't find. So I suppose it removes the root bit from all the disks on the current root volume and puts it on the volume you specify.
Thanks for your answer, Marc
download affects all the disks, so you won't need to redownload the kernel (unless, of course, you're upgrading the kernel at the same time).
Ok (I didn't know if download would only download on the root volume or all of them).
Actually, in 5.1 and later, we only download to file system disks, so you need to be careful of that. But your second volume should have a valid boot image.
Ah! That's the command I didn't find. So I suppose it removes the root bit from all the disks on the current root volume and puts it on the volume you specify.
Yep!
Thanks for your answer, Marc
Glad to be of assistance, Steve
download affects all the disks, so you won't need to redownload the kernel (unless, of course, you're upgrading the kernel at the same time).
In theory that's true, but a couple months back I ran into a bug in 5.0R1 on a 630 after destroying a volume with 22 disks (on a 24 disk filer). The filer wouldn't boot off disk until I booted off floppy and ran download. I think the vol destroy command uses a "hardware erase disk" function. If you erase the vast majority of your disks, you may have trouble the next time you reboot unless you download. The problem was easily repeatable.
I reported the bug to netapp unofficially (since the box was a eval), but never heard if they tracked down the problem. I'd suggest doing the download after the vol destroy/vol create operation even though in theory it's not necessary.
It'd be nice to know if Netapp tracked this one down.
Darrell Root rootd@nas.nasa.gov
Cwaeth Darrell Root:
If you erase the vast majority of your disks, you may have trouble the next time you reboot unless you download. The problem was easily repeatable.
It'd be nice to know if Netapp tracked this one down.
We're currently testing some changes to the boot firmware and the bootblocks that should make booting in this sort of situation more robust. Your situation is a good corner case, and I'll make sure that we test for that possibility, if we haven't already. As always, release information will come out via the usual channels when the software is ready.
I reported the bug to netapp unofficially (since the box was a eval), but never heard if they tracked down the problem. I'd suggest doing the download after the vol destroy/vol create operation even though in theory it's not necessary.
In theory it's not necessary, but downloading again doesn't hurt anything, so at the risk of promulgating a new Urban Filer Legend, I say, "In this case, go ahead and download."
Mike Tuciarone Kernel Porting, Booting, & Other Gross Stuff Network Appliance
In theory that's true, but a couple months back I ran into a bug in 5.0R1 on a 630 after destroying a volume with 22 disks (on a 24 disk filer). The filer wouldn't boot off disk until I booted off floppy and ran download. I think the vol destroy command uses a "hardware erase disk" function.
Nope.
It doesn't do anything to the entire disk, it just changes the disk label to mark the disk as a spare.
I don't think we were able to reproduce it, but we may not have been following the exact same script. Did you create any volumes after destroying the volume but before trying to boot from disk? (That *does* zero the disks in the newly-created volume.)
-
Darrell Root -
guy＠netapp.com -
Marc Merlin -
marc_merlin＠magic.metawire.com -
Michael J. Tuciarone -
Steve Rodrigues