Date: Mon, 17 Feb 2003 19:36:07 -0700 From: elliot schlegelmilch <elliot@cs.montana.edu> To: freebsd-current@freebsd.org Subject: raidframe Message-ID: <20030217193607.A28536@esus.cs.montana.edu>
next in thread | raw e-mail | index | archive | help
hi:
I figured since raidframe was in FreeBSD, it would be a good chance to
try it. I've already used vinum and ccd. I run it in Vmware. I
remember seeing that raidframe is still work in progress. Maybe
something is wrong with my setup. Or maybe it's broken ATM and I
should give it a shot later.
thank you all for your time,
elliot
FreeBSD current-x86.DOMAIN 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 16 19:45:31 EST 2003 elliot@elliot.que.mt.videotron.ca:/usr/obj/usr/current/src/sys/VMWARE i386
# cat raid
START array
1 3 0
START disks
/dev/da0s1e
/dev/da1s1e
/dev/da2s1e
START layout
32 1 1 5
START queue
fifo 100
# raidctl -c /root/raid raid0
RAIDFRAME: protectedSectors is 64
Waiting for DAG engine to start
panic: lockmgr: thread 0xc8f30c94, not exclusive lock holder 0xc8f31620 unlocking
Debugger("panic")
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c05432fc,c05ebbc0,c05419e2,d8527864,1) at Debugger+0x54
panic(c05419e2,c8f30c94,c05419cc,c8f31620,c8f30c94) at panic+0xab
lockmgr(c8f59ce8,6,c8f59c34,c8f30c94,d85278a8) at lockmgr+0x49e
vop_stdunlock(d85278d0,d85278b4,c031b048,d85278d0,d8527910) at vop_stdunlock+0x2f
vop_defaultop(d85278d0,d8527910,c029c59c,d85278d0,d85278cc) at vop_defaultop+0x18
spec_vnoperate(d85278d0,d85278cc,0,c8f7b180,3) at spec_vnoperate+0x18
raidlookup(c8f82800,c8f30c94,d852794c,c05ecc40,258) at raidlookup+0x18c
raid_getcomponentsize(c8f69000,0,0,c8f69000,0) at raid_getcomponentsize+0x47
rf_ConfigureDisk(c8f69000,c8b7f64c,c8f82800,0,0) at rf_ConfigureDisk+0x96
rf_ConfigureDisks(c8f6910c,c8f69000,c8b7f000,1e7,1b7) at rf_ConfigureDisks+0xd1
rf_Configure(c8f69000,c8b7f000,0,d8527afc,c0374c53) at rf_Configure+0xe60
raidctlioctl(c8bdc400,80047201,d8527c54,3,c8f31620) at raidctlioctl+0x358
spec_ioctl(d8527b5c,d8527c28,c03b2071,d8527b5c,d8527b70) at spec_ioctl+0x16e
spec_vnoperate(d8527b5c,d8527b70,c034a04d,c05ecc40,c0565a60) at spec_vnoperate+0x18
vn_ioctl(c8c08000,80047201,d8527c54,c8d0a480,c8f31620) at vn_ioctl+0x1a1
ioctl(c8f31620,d8527d10,c055d207,407,3) at ioctl+0x479
syscall(2f,2f,2f,4,3) at syscall+0x28e
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x804bdff, esp = 0xbfbf7cfc, ebp = 0xbfbf7d18 ---
db> reset
current-x86# disklabel /dev/da0s1
disklabel: ioctl DIOCGDINFO: Inappropriate ioctl for device
current-x86# disklabel -r /dev/da0s1
# /dev/da0s1:
type: SCSI
disk: da0s1
label:
flags:
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 500
sectors/unit: 1024000
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: 1024000 0 unused 0 0 # (Cyl. 0 - 499)
e: 1023936 32 raid # (Cyl. 0*- 499*)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030217193607.A28536>