From owner-freebsd-fs Tue Jan 21 7:44:52 2003 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8D8337B401 for ; Tue, 21 Jan 2003 07:44:49 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBA4943F1E for ; Tue, 21 Jan 2003 07:44:48 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 55256536E; Tue, 21 Jan 2003 16:44:44 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: fs@freebsd.org Subject: Re: RAID alternatives References: From: Dag-Erling Smorgrav Date: Tue, 21 Jan 2003 16:44:44 +0100 In-Reply-To: (Dag-Erling Smorgrav's message of "Tue, 21 Jan 2003 16:15:06 +0100") Message-ID: Lines: 58 User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.2 (i386--freebsd) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --=-=-= Dag-Erling Smorgrav writes: > - RAIDframe: "should be considered highly experimental". Any > experiences with this? Does it work? Is it fast? Is it > reliable? I see it requires wiring down the drive IDs, which > vinum doesn't IIRC. Ho, hum, well, RAIDframe fails to impress me: root@dsa ~# raidctl -c raid0.conf Kernelized RAIDframe activated Searching for raid components... RAIDFRAME: protectedSectors is 64 Waiting for DAG engine to start raid0: rebuilding: raidlookup on device: failed: 2! raidlookup on device: failed! raid0: rebuilding: raidlookup on device: failed: 2! raidlookup on device: failed! raid0: rebuilding: raidlookup on device: failed: 2! raidlookup on device: failed! raid0: rebuilding: raidlookup on device: failed: 2! raidlookup on device: failed! Error: block size on disks (0) must be a power of 2 RAIDFRAME: failed rf_ConfigureDisks with 22 fatal kernel trap: trap entry = 0x2 (memory management fault) faulting va = 0xdeadc0dedeadc0de type = access violation cause = load instructon pc = 0xfffffc00004be3a4 ra = 0xfffffc00004703c4 sp = 0xfffffe000bda1a90 curthread = 0xfffffc000f79f170 pid = 635, comm = raid Stopped at strlen+0x4: ldbu t0,0(a0) <0xdeadc0dedeadc0de> db> trace strlen() at strlen+0x4 kvprintf() at kvprintf+0x634 vsnprintf() at vsnprintf+0x40 panic() at panic+0xb4 _mtx_lock_flags() at _mtx_lock_flags+0x70 msleep() at msleep+0x6e0 DAGExecutionThread() at DAGExecutionThread+0x260 fork_exit() at fork_exit+0xf0 exception_return() at exception_return --- root of call graph --- (see attached configuration file) DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Disposition: attachment; filename=raid0.conf # # Experimental RAID5 configuration # # 1 row, 4 columns, 0 spares START array 1 4 0 # 4 "disks" START disks /dev/da1d /dev/da1e /dev/da1f /dev/da1g # RAID level 5 with 32-sector interleave factor START layout 32 1 1 5 # 100-deep FIFO queue START queue fifo 100 --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message