Date: Thu, 5 Dec 2002 10:13:36 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Adam Laurie <adam@algroup.co.uk> Cc: questions@FreeBSD.org Subject: Re: vinum documentation Message-ID: <20021204234336.GB91963@wantadilla.lemis.com> In-Reply-To: <3DEDCC9D.4000108@algroup.co.uk> References: <3DE244ED.8000903@algroup.co.uk> <20021125224557.GJ41068@wantadilla.lemis.com> <3DE353C7.5080704@algroup.co.uk> <20021126232050.GB21404@wantadilla.lemis.com> <3DE5EAA0.4030009@algroup.co.uk> <20021129020137.GC8307@wantadilla.lemis.com> <3DE74326.7080302@algroup.co.uk> <20021130005821.GD17834@wantadilla.lemis.com> <3DE87950.6000201@algroup.co.uk> <3DEDCC9D.4000108@algroup.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 4 December 2002 at 9:36:29 +0000, Adam Laurie wrote: > Adam Laurie wrote: >> 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. > > .. having now digested what youve said so far, and re-read the docco > several times, i'm guessing the final step would be: > > 6. Run 'vinum makedev' No. 'vinum start' also creates the devices. > 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? Well, it's not correct. When you start vinum, it automatically creates the directory if it's not already there: # ls -l /dev/vinum ls: /dev/vinum: No such file or directory # vinum vinum -> ^D # ls -l /dev/vinum total 1 crw------- 1 root wheel 91, 0x40000001 Dec 5 10:11 Control crw------- 1 root wheel 91, 0x40000002 Dec 5 10:11 control crw------- 1 root wheel 91, 0x40000000 Dec 5 10:11 controld drwxrwxrwx 2 root wheel 512 Dec 5 10:11 drive drwxrwxrwx 2 root wheel 512 Dec 5 10:11 plex drwxrwxrwx 2 root wheel 512 Dec 5 10:11 sd drwxrwxrwx 2 root wheel 512 Dec 5 10:11 vol Running makedev at this point won't do anything else. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021204234336.GB91963>