Date: Fri, 18 Aug 2000 10:56:48 -0400 (EDT) From: Charlie Root <root@palm.cise.ufl.edu> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/20700: vinum create can cause kernel panic Message-ID: <200008181456.KAA00964@palm.cise.ufl.edu>
next in thread | raw e-mail | index | archive | help
>Number: 20700
>Category: kern
>Synopsis: vinum create can cause kernel panic
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Aug 18 08:00:04 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Jim Hranicky (jfh@cise.ufl.edu)
>Release: FreeBSD 4.1-STABLE i386
>Organization:
University of Florida CISE Department
>Environment:
OS ver:
FreeBSD 4.1-STABLE #0
CPU info:
CPU: Pentium III/Pentium III Xeon/Celeron (646.67-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x683 Stepping = 3
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,
MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM>
real memory = 268369920 (262080K bytes)
SCSI Adapter:
ahc1: <Adaptec aic7896/97 Ultra2 SCSI adapter> port 0x2400-0x24ff mem
0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0
ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs
Disk type:
da1: <IBM DMVS36D 0250> Fixed Direct Access SCSI-3 device
da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da1: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
>Description:
The command "vinum create -f /var/tmp/vinum.conf" causes a kernel panic
when accessing a drive set up using the "disklabel" command, and not
/stand/sysinstall :
<root@birch:~> # vinum create -f /var/tmp/vinum.conf
Fatal double fault:
eip = 0xc02f18e9
esp = 0xd6affd7c
ebp = 0xd6affd90
panic: double fault
Debugger("panic")
Stopped at Debugger+0x34: movb $0,0xc03b3be0
db> trace
Debugger(c03328a3) at Debugger+0x34
panic(c0360043,c03605f0,d6affd90,c03605e4,d6affd7c) at panic+0x70
dblfault_handler(0,0,0,0,0) at dblfault_handler+0x47
vinum.conf:
drive d1 device /dev/da1s1e
volume tmpvol
plex name tmpvol.p0 org concat
sd name tmpvol.p0.s0 length 1g drive d1
>How-To-Repeat:
$ ( cd /dev ; ./MAKEDEV da1s1a )
$ disklabel -w -r da1 auto
$ disklabel -e -r da1
Resulting disklabel:
# /dev/da1c:
type: SCSI
disk: IBM
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 4462
sectors/unit: 71687340
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 71687340 0 unused 0 0 # (Cyl. 0 - 4462*)
e: 71687340 0 vinum # (Cyl. 0 - 4462*)
$ vinum create -f /var/tmp/vinum.conf
One of three things have been observed at this point:
1) kernel panic
2) vinum dumps core (I still have the core file)
3) creation of volume with faulty objects, message "Device da1s1e not configured"
However, when the disk config is viewed using /stand/sysinstall fdisk, the partition
is listed as "unused". Apparently, more needs to be done using disklabel, or
/stand/sysinstall must be used to set up disks.
>Fix:
1) Use /stand/sysinstall fdisk to label the disk (I selected "Use entire
partition", type 165 ).
2) disklabel -e -r daX , create vinum partition
3) run "vinum create"
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008181456.KAA00964>