From owner-freebsd-questions@FreeBSD.ORG Tue Nov 25 07:50:58 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E721816A4CE for ; Tue, 25 Nov 2003 07:50:58 -0800 (PST) Received: from yoda.anything-inc.com (adsl-068-153-193-052.sip.bct.bellsouth.net [68.153.193.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FFAA43FF2 for ; Tue, 25 Nov 2003 07:50:57 -0800 (PST) (envelope-from bobc@anything-inc.com) Received: from neo (68.153.193.50:4954)Server] ; Tue, 25 Nov 2003 11:00:33 -0500 From: "Bob Collins" To: FreeBSD Date: Tue, 25 Nov 2003 10:46:21 -0500 MIME-Version: 1.0 Message-ID: <3FC332FD.8650.5580580@localhost> Priority: normal In-reply-to: <20031123224649.GK82843@wantadilla.lemis.com> References: <5.2.0.9.0.20031123130031.00a9a020@anything-inc.com> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Spam-Status: No, hits=-2.5 required=3.5 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: Re: Disklabel problem IBM SCSI3 disks, vinum too X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 15:50:59 -0000 Date sent: Mon, 24 Nov 2003 09:16:49 +1030 From: "Greg 'groggy' Lehey" To: "Bob Collins" Organization: The FreeBSD Project Copies to: FreeBSD Subject: Re: Disklabel problem IBM SCSI3 disks, vinum too [Format recovered--see http://www.lemis.com/email/email-format.html] Single-line paragraphs. On Sunday, 23 November 2003 at 13:03:47 -0500, Bob Collins wrote: > At 07:30 PM 11/21/2003, you wrote: >> On Friday, 21 November 2003 at 9:25:58 -0500, Bob Collins wrote: >>> vinum -> list >>> 4 drives: >>> D d State: up Device /dev/da1s1h Avail: 0/8747 MB (0%) >>> D c State: up Device /dev/da2s1h Avail: 0/8747 MB (0%) >>> D b State: up Device /dev/da3s1h Avail: 0/8747 MB (0%) >>> D a State: up Device /dev/da4s1h Avail: 0/8747 MB (0%) >>> >>> 1 volumes: >>> V raid State: down Plexes: 1 Size: 25 GB >>> >>> 1 plexes: >>> P raid.p0 R5 State: init Subdisks: 4 Size: 25 GB >>> >>> 4 subdisks: >>> S raid.p0.s0 State: empty PO: 0 B Size: 8747 MB >>> S raid.p0.s1 State: empty PO: 512 kB Size: 8747 MB >>> S raid.p0.s2 State: empty PO: 1024 kB Size: 8747 MB >>> S raid.p0.s3 State: empty PO: 1536 kB Size: 8747 MB >> >> This doesn't agree with what you say above. It also looks fine to >> me. > > My apologies, Greg. Quite right. I was messing with the system right > before the response about sa4 device nodes in /dev. Once I made the > da4 devices, then the disklabel worked. My mistake jumping the gun. > > One follow-up question if I may. > > I assume that the init process for a RAID5 takes quite some time, > no? This has been in the init stage for 3 days. The vinum daemon is > running as I can see it listed in ps -ax. This is the init state, which means it needs initializing. To initialize, issue the 'init' command. The state will change from 'init' to 'initializing', and the list command shows the progress of the initialization. This writes zeroes to the drives in parallel; expect it to take an hour or two on drives of this size. Greg -- Thanks Greg, that did the trick. The initialization only took 19 minutes. The newfs took about 5 minutes, and it is now running perfectly. Thank you again. Bob -- Bob Collins Anything-inc.com