From owner-freebsd-hackers Wed Nov 14 0: 5:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by hub.freebsd.org (Postfix) with ESMTP id 1EEF237B417; Wed, 14 Nov 2001 00:05:31 -0800 (PST) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtpzilla3.xs4all.nl (8.12.0/8.12.0) with ESMTP id fAE85KcO011407; Wed, 14 Nov 2001 09:05:20 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.11.6/8.9.3) with ESMTP id fAE85JT34436; Wed, 14 Nov 2001 09:05:19 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200111140805.fAE85JT34436@trantor.xs4all.nl> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Greg Lehey Cc: Paul van der Zwan , Mike Smith , sos@freebsd.dk, john_wilson100@excite.com, freebsd-hackers@FreeBSD.org, sos@FreeBSD.org, paulz@trantor.xs4all.nl Subject: Re: HPT370 RAID or Vinum? In-Reply-To: Message from Greg Lehey of "Wed, 14 Nov 2001 11:08:28 +1030." <20011114110828.A42750@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Nov 2001 09:05:19 +0100 From: Paul van der Zwan Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011114110828.A42750@monorchid.lemis.com>, Greg Lehey wrote: >On Sunday, 11 November 2001 at 22:37:58 +0100, Paul van der Zwan wrote: >> In message <200111112105.fABL54801504@mass.dis.org>, Mike Smith wrote: >>>>> These "cheap controllers" don't have any algorithms at all to speak of; >>>>> they're just ATA controllers with BIOS code that supposedly understands >>>>> striping/mirroring. >>>> >>>> There is no algorithm to speak of involved with striping, and just >>>> a little more in mirroring in the error case, but anyways.. >>> >>> Unless you've fixed it, the error case handling in mirror mode is busted >>> as well. >>> >>>>> The "algorithms" are in the 'ar' driver, which should really just be a >>>>> vinum shim. >>>> >>>> Well, the way vinum is implemented that wont work unfortunately. >>> >>> There's no reason that 'ar' and Vinum couldn't be fixed to play together. >>> >>> Or at least, no technical reason. > >Indeed. It works. > >> Well, currently there are some minor glitches. I just installed a >> vinum slice on /dev/ar0s1 and unless I do a 'vinum read /dev/ar0s1' >> vinum will not find the volumes. This causes the boot of my box ( >> -current btw) to fail at the mount of my filesystems. Is there a >> way to tell vinum to also look on /dev/ar* for its config?? > >This may be because ar doesn't have a devstat interface (my >assumption). Currently Vinum looks in the devstat structures to find >mass storage devices, but this will change when the root file system >support gets rewritten (hopefully Real Soon Now). Well for the moment I 'fixed' it by marking them as noauto in /etc/fstab and having the following in /etc/rc.local: vinum read /dev/ar0s1 mount /usr/source mount /usr/obj Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message