From owner-freebsd-geom@FreeBSD.ORG Tue Sep 12 14:22:33 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C55E16A47B for ; Tue, 12 Sep 2006 14:22:33 +0000 (UTC) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id D475C43D7D for ; Tue, 12 Sep 2006 14:22:28 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from gaiahost.coop (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Tue, 12 Sep 2006 10:22:26 -0400 id 00794091.4506C2A3.000019BC Received: by gaiahost.coop (sSMTP sendmail emulation); Tue, 12 Sep 2006 10:22:33 -0400 Date: Tue, 12 Sep 2006 10:22:33 -0400 From: Mark Bucciarelli To: freebsd-geom@FreeBSD.org Message-ID: <20060912142232.GB440@rabbit> Mail-Followup-To: freebsd-geom@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: gvinum raid5 in production X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Sep 2006 14:22:33 -0000 Is anybody using gvinum raid5 in production with 6.1-release? How is it going? Have you every had any instances where a kernel panic caused the raid-array not to rebuild properly on reboot and you had data loss? Has your array been robust to SCSI errors from your drives? I reviewed all problem reports I could find and only 89660 looked serious. Dec. 2005 (6.0): kernel panic (perhaps due to low memory) caused by code in geom perhaps. Looks like raid rebuilds properly, only b/c poster didn't mention any problem. Patch included. (Hmmm, gvinum code doesn't check for null pointers returned by malloc.) [1] Sep. 2005 (6.0): probably not geom-related (according to poster). Kernel panic when copying large file (2 Gb). [2] Feb. 2005 (5.3): A newfs bug caused by an integer overflow when entering stupidly large values when creating a new file system. No risk. [3] Nov. 2005 (5.3): Pulls a drive from raid 5 (w/o turning off machine, I _think_), get's SCSI errors, and kernel panics. Older machine? (Pentium Pro) [4] As a followup question, in case of kernel panic, coredump and subsequent savecore, is it safe to have swap on a gmirror raid1? How about on gvinum raid 5? m [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89660 [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85728 [3] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77181 [4] http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/73830