Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Oct 1998 21:52:21 -0700
From:      brian@worldcontrol.com
To:        freebsd-current@FreeBSD.ORG
Cc:        grog@lemis.com
Subject:   can't get vinum to work
Message-ID:  <19981018215221.A27539@top.worldcontrol.com>

next in thread | raw e-mail | index | archive | help
I was about to setup ccd running two drives striped, when I found
that vinum, while in beta, seems to be the future.

However, I get various failures.

I'm running -current,elf,CAM.

My vinum init file look like:
# Drives
drive drive1 device /dev/da1h 
drive drive2 device /dev/da2h 
# volume
volume bigvol
 plex org striped 64b
  sd length 2030m drive drive1
  sd length 2030m drive drive2

However when I run:

bls2# vinum resetconfig
bls2# vinum create /etc/rc.vinum 

** 2 Can't initialize drive drive1: Invalid argument
** 3 Can't initialize drive drive2: Invalid argument
** 7 Drive drive1 is not accessible: Input/output error
** 8 Unnamed sd is not associated with a plex: Invalid argument
Can't save Vinum config: Operation not permitted
Configuration summary

Drives:         2 (4 configured)
Volumes:        1 (4 configured)
Plexes:         1 (8 configured)
Subdisks:       2 (16 configured)

D drive1                State: down     Device /dev/da1h
D drive2                State: down     Device /dev/da2h

V bigvol                State: down     Plexes:       1 Size:       2030 MB

P bigvol.p0           S State: down     Subdisks:     1 Size:       2030 MB

S bigvol.p0.s0          State: down     PO:        0  B Size:       2030 MB

with these messages in /var/log/messages:

Oct 18 21:15:15 bls2 vinum: configuration obliterated
Oct 18 21:15:26 bls2 /kernel: vinum: drive drive1 is down
Oct 18 21:15:26 bls2 /kernel: vinum open_drive /dev/da1h: failed with error 22
Oct 18 21:15:26 bls2 /kernel: vinum: drive drive2 is down
Oct 18 21:15:26 bls2 /kernel: vinum open_drive /dev/da2h: failed with error 22
Oct 18 21:15:26 bls2 /kernel: vinum: plex bigvol.p0 does not have at least 2 subdisks



If I use da1/da2 instead of da1h/da2h, I get this instead:

bls2# vinum resetconfig
bls2# vinum create /etc/rc.vinum 
Can't save Vinum config: Operation not permitted
Configuration summary

Drives:         2 (4 configured)
Volumes:        1 (4 configured)
Plexes:         1 (8 configured)
Subdisks:       2 (16 configured)

D drive1                State: down     Device /dev/da1
D drive2                State: down     Device /dev/da2

V bigvol                State: up       Plexes:       1 Size:       4060 MB

P bigvol.p0           S State: down     Subdisks:     2 Size:       4060 MB

S bigvol.p0.s0          State: down     PO:        0  B Size:       2030 MB
S bigvol.p0.s1          State: down     PO:     2030 MB Size:       2030 MB

with these messages in /var/log/messages:

Oct 18 21:19:55 bls2 vinum: configuration obliterated
Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is up
Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is up
Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is up 
Oct 18 21:19:59 bls2 /kernel: vinum: volume bigvol is up
Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da1, error 19
Oct 18 21:19:59 bls2 /kernel: vinum: drive drive1 is down
Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s0 is down
Oct 18 21:19:59 bls2 /kernel: vinum: plex bigvol.p0 is degraded
Oct 18 21:19:59 bls2 /kernel: vinum: Can't write config to /dev/da2, error 19
Oct 18 21:19:59 bls2 /kernel: vinum: drive drive2 is down 
Oct 18 21:19:59 bls2 /kernel: vinum: subdisk bigvol.p0.s1 is down
Oct 18 21:20:00 bls2 /kernel: vinum: plex bigvol.p0 is down


here is some more support info:

bls2# fdisk da1
******* Working on device /dev/rda1 *******
parameters extracted from in-core disklabel are:
cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

bls2# fdisk da2
******* Working on device /dev/rda2 *******
parameters extracted from in-core disklabel are:
cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2063 heads=64 sectors/track=32 (2048 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
<UNUSED>
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

>From dmesg:

kernel: da2 at ahc0 bus 0 target 5 lun 0
kernel: da2: <IBM DCAS-32160W S65A> Fixed Direct Access SCSI2 device 
kernel: da2: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled
kernel: da2: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C)
kernel: da1 at ahc0 bus 0 target 4 lun 0
kernel: da1: <IBM DCAS-32160W S65A> Fixed Direct Access SCSI2 device
kernel: da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled
kernel: da1: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C)

And in case you are wondering:

bls2# modstat
Type     Id Off Loadaddr Size Info     Rev Module Name
MISC      0   0 f41fc000 0269 f4206054   1 vinum_mod

-- 
Brian Litzinger <brian@litzinger.com>

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?19981018215221.A27539>