Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Jan 2001 21:48:29 +1030
From:      Greg Lehey <grog@lemis.com>
To:        Josef Karthauser <joe@tao.org.uk>
Cc:        Thomas Seck <tmseck@web.de>, freebsd-stable@FreeBSD.ORG
Subject:   Re: Vinum safe to use for raid 0?
Message-ID:  <20010103214829.X4336@wantadilla.lemis.com>
In-Reply-To: <20010103102943.A770@tao.org.uk>; from joe@tao.org.uk on Wed, Jan 03, 2001 at 10:29:44AM %2B0000
References:  <20010102230107.A559@basildon.homerun> <20010103102943.A770@tao.org.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday,  3 January 2001 at 10:29:44 +0000, Josef Karthauser wrote:
> On Tue, Jan 02, 2001 at 11:01:07PM +0100, Thomas Seck wrote:
>> Hi all,
>>
>> sorry if this is OT for -stable, but I followed the discussion about
>> vinum in here and got a bit worried.
>>
>> I am currently deploying a proxy server for our company. It shall use
>> squid on 4.2-STABLE. I would like to put the cache data on a vinum RAID
>> 0, made of three U160 disks. As I understood the discussion so far,
>> there are some unresolved problems with the raid 5 code. Could someone
>> tell me whether I can safely use vinum for building a raid 0 system
>> (despite the fact that the HW may be a point of failure of course)?
>
> As far as I'm aware there are no problems using vinum for raid 0.
>
> As far as I understand from Greg he's not aware of many people who
> are having problems with raid 5.

Probably.  If you know of somebody I don't know of, please let me
know.

> As one of the small minority who was having problems I'd advice you
> to soaktest any vinum raid 5 installation before committing
> important data to it.

That's what vinum(4) says.

Greg
--
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010103214829.X4336>