Date: Sat, 12 Aug 2000 10:16:13 -0500 From: "Guy Gustavson" <bigfoot@stomped.com> To: <questions@FreeBSD.ORG> Subject: disklabel fails on da4 Message-ID: <NEBBLIFEMLAKOGJKEAINGEFOCBAA.bigfoot@stomped.com> In-Reply-To: <bulk.51886.20000807213306@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I've got 5 identical SCSI drives in a system that I want to use vinum on. It also has a IDE drive that is being used as the native boot file system and swap. I've been having a hell of time getting vinum to configure solidly on this system. dmesg shows the drives, last time I tried to create a config in vinum it panic'd the box. Notice how when vinum is loaded it see's the drives, but when I interrogate the drives from the vinum command prompt it knows nothing about them? da0 at ahc0 bus 0 target 0 lun 0 da0: <QUANTUM ATLAS_V_36_SCA 0230> Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35020MB (71722776 512 byte sectors: 255H 63S/T 4464C) da1 at ahc0 bus 0 target 1 lun 0 da1: <QUANTUM ATLAS_V_36_SCA 0230> Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 35020MB (71722776 512 byte sectors: 255H 63S/T 4464C) da2 at ahc0 bus 0 target 2 lun 0 da2: <QUANTUM ATLAS_V_36_SCA 0230> Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35020MB (71722776 512 byte sectors: 255H 63S/T 4464C) da3 at ahc0 bus 0 target 3 lun 0 da3: <QUANTUM ATLAS_V_36_SCA 0230> Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 35020MB (71722776 512 byte sectors: 255H 63S/T 4464C) da4 at ahc0 bus 0 target 4 lun 0 da4: <QUANTUM ATLAS_V_36_SCA 0230> Fixed Direct Access SCSI-3 device da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 35020MB (71722776 512 byte sectors: 255H 63S/T 4464C) Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted vinum: loaded vinum: CONFIGURATION OBLITERATED vinum: drive drive0 is up vinum: drive d0 is up vinum: drive d0 is up titan# vinum vinum -> list 0 drives: 0 volumes: 0 plexes: 0 subdisks: vinum -> info Flags: 0x80004 Total of 4 blocks malloced, total memory: 1776 Maximum allocs: 7, malloc table at 0xc267ae60 0 requests active, maximum 0 active vinum -> So I figured I would wipe the drives partition info and start over, when I noticed this... titan# titan# titan# titan# dd if=/dev/zero of=/dev/rda0 count=200 200+0 records in 200+0 records out 102400 bytes transferred in 0.060441 secs (1694214 bytes/sec) titan# dd if=/dev/zero of=/dev/rda1 count=200 200+0 records in 200+0 records out 102400 bytes transferred in 0.058273 secs (1757247 bytes/sec) titan# dd if=/dev/zero of=/dev/rda2 count=200 200+0 records in 200+0 records out 102400 bytes transferred in 0.058143 secs (1761174 bytes/sec) titan# dd if=/dev/zero of=/dev/rda3 count=200 200+0 records in 200+0 records out 102400 bytes transferred in 0.058118 secs (1761933 bytes/sec) titan# dd if=/dev/zero of=/dev/rda4 count=200 200+0 records in 200+0 records out 102400 bytes transferred in 0.058126 secs (1761691 bytes/sec) titan# dd if=/dev/zero of=/dev/rda5 count=200 200+0 records in 200+0 records out 102400 bytes transferred in 0.005801 secs (17652243 bytes/sec) titan# disklabel -r da0 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) titan# disklabel -w -r da0 auto titan# disklabel -w -r da1 auto titan# disklabel -w -r da2 auto titan# disklabel -w -r da3 auto titan# disklabel -w -r da4 auto disklabel: ioctl DIOCWLABEL: Operation not supported by device titan# Why does da4 fail on the disklabel operation? This is fresh install of 4.1-RELEASE, I just installed it, and started working with vinum. Someone should really write a "kosher" procedure for labeling vinum drives. da0 - da4 are specifically reserved for vinum use, no other data will be on them. This is the config I'm trying for..... titan# cat vinum.conf drive d1 device /dev/da0e drive d2 device /dev/da1e drive d3 device /dev/da2e drive d4 device /dev/da3e drive d5 device /dev/da4e volume titan1 plex org raid5 512k sd length 11g drive d1 sd length 11g drive d2 sd length 11g drive d3 sd length 11g drive d4 sd length 11g drive d5 volume titan2 plex org raid5 512k sd length 11g drive d1 sd length 11g drive d2 sd length 11g drive d3 sd length 11g drive d4 sd length 11g drive d5 volume titan3 plex org raid5 512k sd length 0 drive d1 sd length 0 drive d2 sd length 0 drive d3 sd length 0 drive d4 sd length 0 drive d5 titan# which should more or less split the drives up into three equal pieces. ================================================================ Guy Gustavson | bigfoot@stomped.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NEBBLIFEMLAKOGJKEAINGEFOCBAA.bigfoot>