From owner-freebsd-stable Sun Mar 18 13:21:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id B686F37B71B for ; Sun, 18 Mar 2001 12:45:23 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2IKlmL00993; Sun, 18 Mar 2001 12:47:48 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103182047.f2IKlmL00993@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: rand@meridian-enviro.com Cc: Mike Tancsa , freebsd-stable@FreeBSD.ORG, bryanh@meridian-enviro.com Subject: Re: 3ware problems In-reply-to: Your message of "Sun, 18 Mar 2001 12:50:36 CST." <87elvu6hdv.wl@localhost.meridian-enviro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Mar 2001 12:47:48 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The first time I did this I thought something was broken when I > watched the newfs output those duplicate super block locations. It was > about 10 seconds between each block! After a search of the FreeBSD > lists I found a reference to initializing the array, and just waited. > > On ttyv1 the kernel issues a message when the array initialization is > done, so I usually just wait for that. Newfs is even more pessimal, due to the alignment fixup the driver has to perform. However, the array is perfectly usable while it's being initialised. Just. Dog. Slow. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message