From owner-freebsd-stable Wed Nov 8 1:51:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from io.cuk.nu (node.068.lc.link.si [212.30.95.68]) by hub.freebsd.org (Postfix) with ESMTP id 4140937B678 for ; Wed, 8 Nov 2000 01:51:34 -0800 (PST) Received: from cuk.nu (nu.cuk.nu [212.30.95.50]) by io.cuk.nu (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA27963; Mon, 6 Nov 2000 22:25:03 +0100 Message-ID: <3A072196.D9DA9EF3@cuk.nu> Date: Mon, 06 Nov 2000 22:24:38 +0100 From: Marko Cuk X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: Roman Shterenzon , freebsd-stable@FreeBSD.ORG Subject: Re: Stability References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roman Shterenzon wrote: > > I've a perfectly good PR about vinum (panics) open. There's no even single > follow up (kern/22103). > I couldn't stand it any longer, so I'm not able to recreate it since I'm > using raid1 on those disks now. I waited for almost one month but > aparently nothing was done. (I opened one PR before that but it was badly > formatted and had to become closed). > > I understand that people have other things to do, and FreeBSD is volunteer > project, but we shall face the truth - the man page for vinum should state > that RAID5 is experimental and prone to crashes. It should be emphasized > that it shouldn't be used in sensitive environmets. > I know other people for whom it rendered their servers unusable. > > I managed 8( to crash it today as well. I'll probably move to hardware > raid solution instead, I'm quite fed up with vinum. > Wich good hardware solution is supported under FreeBSD ? > I've a crash dump of today, perhaps I'll open another PR. > I've had crash before one hour, and I've only doing cvsup ports .... Yesterday I was changing speed of ipfw pipe and it crashed after a second. I cannot imagine such things. I can't have 20 days of uptime because of so many crashes. Yes, I know a solution for stable FreeBSD. Leave it completly alone and don't do anything. It's no good. Fbsd is 4.1. Cuk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message