In message <[EMAIL PROTECTED]>, Greg Lehey wrote:
>On Sunday, 11 November 2001 at 22:37:58 +0100, Paul van der Zwan wrote:
>> In message <[EMAIL PROTECTED]>, 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to