From owner-freebsd-questions Mon Mar 17 8:37:58 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 469C637B401 for ; Mon, 17 Mar 2003 08:37:57 -0800 (PST) Received: from MX1.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 926A843F85 for ; Mon, 17 Mar 2003 08:37:55 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-37-50-dsl.mus.estpak.ee [80.235.37.50]) by MX1.estpak.ee (Postfix) with ESMTP id E209F88846; Mon, 17 Mar 2003 18:36:30 +0200 (EET) Received: (from vallo@localhost) by kevad.internal (8.12.6/8.12.6/Submit) id h2HGblp0003791; Mon, 17 Mar 2003 18:37:47 +0200 (EET) (envelope-from vallo) Date: Mon, 17 Mar 2003 18:37:46 +0200 From: Vallo Kallaste To: Scott Mitchell Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Strange crash, possibly vinum-related Message-ID: <20030317163746.GA3584@kevad.internal> Reply-To: kalts@estpak.ee References: <20030310231532.GD522@tuatara.fishballoon.org> <20030317105828.GA23237@tuatara.fishballoon.org> <20030317115752.GA2250@kevad.internal> <20030317121932.GA23991@tuatara.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030317121932.GA23991@tuatara.fishballoon.org> User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 17, 2003 at 12:19:32PM +0000, Scott Mitchell wrote: > Thanks -- you've confirmed what I suspected, that I could have avoided the > problems I saw by being a bit more cautious. My bad. > > Out of interest though, why do you advise not putting critical data on a > Vinum R5 volume? This one has been running fine for ~2 years under > reasonable loads. The disk failure was the first time it's required any > attention at all, and it seems the problems I had with that were mostly of > my own making. The mailing lists don't seem to be overrun with people > complaining that 'Vinum ate my files' :-) Because RAID5 main features are to increase data redundancy _and_ data availability. As you have discovered, it runs until it fails and then you'll have a hard time recovering it. Recovery is the most important (and difficult) part of it. When it fails to recover from the disk loss, what it's worth, then? The 2 years of uninterrupted service doesn't matter when it happens. Your data is unavailable and services down. Critical data is, by definition, critical :) I did put lots of data onto Vinum R5, because I did know that a day of downtime per half a year isn't problem. Recovery on the quiet (unmounted) volume did work and all was well. But for critical data I don't trust it (yet). Just my point of view. -- Vallo Kallaste To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message