Disklabel problem IBM SCSI3 disks, vinum too

[Bob Collins]

Date sent:      	Mon, 24 Nov 2003 09:16:49 +1030
From:           	"Greg 'groggy' Lehey" <grog at freebsd.org>
To:             	"Bob Collins" <freebsd at anything-inc.com>
Organization:   	The FreeBSD Project
Copies to:      	FreeBSD <freebsd-questions at freebsd.org>
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