From owner-freebsd-stable Wed Dec 1 6: 4:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id DA2C614D68 for ; Wed, 1 Dec 1999 06:04:55 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id PAA25851; Wed, 1 Dec 1999 15:04:53 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id PAA11273; Wed, 1 Dec 1999 15:04:42 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <14405.8810.777783.992833@trooper.velocet.net> References: <14405.8810.777783.992833@trooper.velocet.net> Date: Wed, 1 Dec 1999 15:03:34 +0100 To: David Gilbert , stable@FreeBSD.ORG From: Brad Knowles Subject: Re: vinum experiences. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:28 AM -0500 1999/12/1, David Gilbert wrote: > 1. Removing a device (at least, with the ahc controller) locks the bus > even though I have a RAID hot-swap ready chassy (that properly > isolates the bus between commands). In my test, I had a completely > quiet SCSI bus when I removed one of the drives. I then wrote to the > RAID array. I got: Vinum does not (currently) support any kind of hot-swap capability. See and . > 2. It's not obvious how to replace a dead drive with vinum. I have > tried several times to perform this action without success. Vinum > attach says it should do it. It refuses. Assuming that the system has been safely shutdown and is physically powered off, I believe that the following process will work: 1. Remove the old drive, noting it's physical position in the SCSI chain, it's SCSI id, it's termination status, etc... 2. Replace the drive with an *identical* new one (same model number, same number of heads and platters, same firmware revision, etc...), and make sure that the new drive sits in the same physical position in the SCSI chain, has the same SCSI id, same termination status, etc... 3. Reboot the machine. 4. Bring up vinum (but don't attempt to mount the affected filesystem) and init the drive. 5. Use the "rebuildparity" command to start the recovery process. 6. When complete, try mounting the filesystem. Of course, I haven't actually tested this procedure (and I hope I never have to), so YMMV and use at your own risk. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message