kern/59205: vinum doesn't check whether strip size is non-0 for raid5

[hb at freebsd.x256.org &]

>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 at 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: