From owner-freebsd-bugs@FreeBSD.ORG Tue Nov 11 23:00:40 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82A5516A4CE for ; Tue, 11 Nov 2003 23:00:40 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C93643FDD for ; Tue, 11 Nov 2003 23:00:38 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hAC70cFY042171 for ; Tue, 11 Nov 2003 23:00:38 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id hAC70cDh042170; Tue, 11 Nov 2003 23:00:38 -0800 (PST) (envelope-from gnats) Resent-Date: Tue, 11 Nov 2003 23:00:38 -0800 (PST) Resent-Message-Id: <200311120700.hAC70cDh042170@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "hb@freebsd.x256.org &" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7C4416A4CE for ; Tue, 11 Nov 2003 22:52:30 -0800 (PST) Received: from monger.x256.com (d64-180-80-190.bchsia.telus.net [64.180.80.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2B0243FD7 for ; Tue, 11 Nov 2003 22:52:29 -0800 (PST) (envelope-from root@monger.x256.com) Received: from monger.x256.com (localhost.x256.com [127.0.0.1]) by monger.x256.com (8.12.9/8.12.9) with ESMTP id hABN2VDS000800 for ; Tue, 11 Nov 2003 15:02:31 -0800 (PST) (envelope-from root@monger.x256.com) Received: (from root@localhost) by monger.x256.com (8.12.9/8.12.9/Submit) id hABN2VO1000799; Tue, 11 Nov 2003 15:02:31 -0800 (PST) Message-Id: <200311112302.hABN2VO1000799@monger.x256.com> Date: Tue, 11 Nov 2003 15:02:31 -0800 (PST) From: "hb@freebsd.x256.org &" To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: kern/59205: vinum doesn't check whether strip size is non-0 for raid5 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "hb@freebsd.x256.org &" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Nov 2003 07:00:40 -0000 >Number: 59205 >Category: kern >Synopsis: vinum doesn't check whether strip size is non-0 for raid5 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Nov 11 23:00:37 PST 2003 >Closed-Date: >Last-Modified: >Originator: Nicholas Vinen & >Release: FreeBSD 5.1-RELEASE i386 >Organization: None >Environment: System: FreeBSD monger.x256.com 5.1-RELEASE FreeBSD 5.1-RELEASE #2: Tue Nov 11 08:53:36 PST 2003 root@monger.x256.com:/usr/src/sys/i386/compile/MONGER i386 >Description: If no stripe size is specified for a raid5 plex in vinum, the default seems to be set at 0. This causes the machine to crash/reboot when any data is written to the volume which contains the plex. >How-To-Repeat: drive d1 device /dev/ad4s1a drive d2 device /dev/ad6s1a drive d3 device /dev/ad8s1a drive d4 device /dev/ad10s1a drive d5 device /dev/ad12s1a drive d6 device /dev/ad14s1a drive d7 device /dev/ad16s1a drive d8 device /dev/ad18s1a volume raid setupstate plex org raid5 sd length 1000m drive d1 sd length 1000m drive d2 sd length 1000m drive d3 sd length 1000m drive d4 sd length 1000m drive d5 sd length 1000m drive d6 sd length 1000m drive d7 sd length 1000m drive d8 or something like that.... then "vinum create foo" and "newfs /dev/vinum/raid" >Fix: vinum probably shouldn't let one create a plex using raid5 without a sensible stripe size (positive, and greater than or equal to 1k say). Also the kernel should check, not just the user space program. >Release-Note: >Audit-Trail: >Unformatted: