Adam Laurie wrote:
.. having now digested what youve said so far, and re-read the docco several times, i'm guessing the final step would be:Greg 'groggy' Lehey wrote:describe the procedure for unplugging the external chassis from machine A, and plugging it into machine B, and bringing up the vinum RAID without re-initialising it (i.e. preserving the data already on it).1. On machine A, stop Vinum. Depending on the hardware, you may need to shut down. 2. Remove the chassis from machine A. 3. Connect the chassis to machine B. Depending on the hardware, you may need to shut down. 4. If you haven't rebooted machine B, run camcontrol rescan on the SCSI bus to discover the new disks. 5. Run 'vinum start'.
are you saying that at this point vinum will scan all disk busses and decide for itself that the raid exists, and reconstruct /dev/vinum?
i know you've said in a previous post that /dev/vinum "isn't important", but since it contains mount points etc, i assume it's reasonably vital... anyway, our experience when we complete the steps above was that /dev/vinum/raid1 etc. didn't exist, so we couldn't mount the volume, which is why we went on to perform the other steps i described.
6. Run 'vinum makedev'
in which case our mistake was doing this and 'vinum start' the wrong way around (and then going on to compund the problem in various other ways... :)
does this make sense?
cheers,
Adam
--
Adam Laurie Tel: +44 (20) 8742 0755
A.L. Digital Ltd. Fax: +44 (20) 8742 5995
The Stores http://www.thebunker.net
2 Bath Road http://www.aldigital.co.uk
London W4 1LT mailto:[EMAIL PROTECTED]
UNITED KINGDOM PGP key on keyservers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message