Matt,

You may need to refer to the rehoming a foreign volume bit on the NOW site. I have pasted relevent extracts below.

********** Extract 1 **********

Installing a foreign volume

BM_1149726You can remove an entire volume from one filer and install it in another, which makes the moved volume a foreign volume to the filer.

BM_1178353 Example

BM_1178361For example, you might want to move a volume to a different filer to

BM_1149727 * replace the volume's disk shelf with one that has a greater storage capacity BM_1149728

* gain access to the files on a dead filer

BM_1149729When a filer detects a foreign volume at boot time, it places the foreign volume off-line. You can then bring the foreign volume on-line. For more information about installing and bringing up a foreign volume on-line, refer to "Adding http://now.netapp.com/NOW/knowledge/docs/ontap/rel523/html/sag/disk5.htm#11 49886 a foreign volume."

********** Extract 2 **********

Adding a foreign volume

BM_1149888To add a foreign volume, that is, a volume that was previously installed on another filer, you move the disks that contain the volume from the old filer to the destination filer.

BM_1179040Complete the following steps to add a foreign volume.

BM_1181660BM_1177101Step BM_1177103Action

BM_11771051 BM_1177107Follow the instructions in the hardware guide to remove the disks from the old filer.

BM_11771092 BM_1177111

Turn off the destination filer and install the disks in the destination filer's disk shelf.

BM_11771133 BM_1177115

Turn on and boot the destination filer.

BM_1177116 Results

BM_1185503When the destination filer boots, it places the foreign volume off-line. If the foreign volume has the same name as an existing volume on the filer, the filer renames it volume_name(1), where volume_name is the original name of the volume.

BM_1185881 _____

Caution: If the foreign volume is incomplete, repeat Steps 1 and 2 to add the missing disks. Do not try to add missing disks while online--doing so will cause them to become hot spare disks.

BM_1185905 _____

BM_11855354 BM_1185564

If the filer renamed the foreign volume because of a name conflict, type the following command to rename the volume:

BM_1185589vol rename oldname newname

BM_1185565 Example

BM_1185566The following command renames the volume vol0(1) to vol1:

BM_1185567vol rename vol0(1) vol1

BM_11771225 BM_1177124

Type the following command to bring the volume on-line in the new filer, replacing volume_name with the name of the volume:

BM_1177133vol online volume_name

BM_11791026 BM_1179104

Enter the following command to confirm that the added volume came on-line:

BM_1179129vol status

BM_1149894 Destroying a volume

BM_1149896To destroy a volume, turning its disks back into spare disks, follow these steps.

BM_1181656BM_1177162Step BM_1177164Action

BM_11771661 BM_1177168To deactivate the volume, enter BM_1177195

vol offline volume

BM_11771702 BM_1177172Enter the reboot command to reboot the filer.

BM_11771743 BM_1177176To destroy the volume, enter BM_1177211

vol destroy volume

BM_1149900 Renaming a volume

BM_1149902To rename a volume, follow these steps.

BM_1181649BM_1177221Step BM_1177223Action

BM_11772251 BM_1177227Enter BM_1177242

vol rename oldvolume newvol

BM_11772292 BM_1177231Update the /etc/exports file and run exportfs.

BM_11772333 BM_1177235Update any CIFS shares that refer to the volume.

BM_1177293 Handling volume failures

BM_1177295A volume might fail because of an inconsistent directory or a double-disk failure. If the system does not reboot after a volume failure, take the volume off-line, as follows:

BM_1177296 1. Boot the filer from a system boot diskette into maintenance mode. BM_1177297

2. Use the vol command to take the failed volume off-line.

BM_1177298If the failed volume was the filer's root volume, you must designate another volume as the new root volume.

_____

There may also be issues with moving a root volume between filers ie 760 ----> 840. Just data volumes should be fine.

I hope this is of help,

Jason

-----Original Message----- From: Matt Phelps [ mailto:mphelps@cfa.harvard.edu mailto:mphelps@cfa.harvard.edu ] Sent: 31 January 2001 16:44 To: toasters@mathworks.com Subject: Physically moving a volume

All,

We are physically moving a disk volume from a 760 to an 840 tonight. We're resonably confident about bringing up the 840 with the moved disks on it. The volume will come up as a foreign volume (it won't need to be renamed) and we'll just need to do a "vol online" command for it. It's not a root volume.

However, the book says to check "your hardware guide" for instructions on removing the disks from the 760. We can't find this anywhere. Our current plan is to remove references to the volume in the various /vol0/etc files; shut down the 760, power it and it's shelves off. Remove the disks and just power everything back on again.

Is it that simple?

-- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps@cfa.harvard.edu, http://cfa-www.harvard.edu/~mphelps http://cfa-www.harvard.edu/~mphelps