Partition c represents the whole harddisk and should be used
for any file system.
Using disklabel create a partition a with fstype vinum and
change your vinum.conf to use /dev/ad2a and /dev/ad3a
For me it is still working in 4.2-STABLE I got last week
Vinesh
> -----Original Message-----
> From: Shawn Ostapuk [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, April 23, 2001 3:47 PM
> To: [EMAIL PROTECTED]
> Subject: vinum configuration
>
> After upgrading to 4.3 from 4.2 my vinum configuration seems
> to have stopped working.
>
>
> this is my vinum.conf file:
>
> drive vinumdrive0 device /dev/ad2c
> drive vinumdrive1 device /dev/ad3c
> volume vimum0
> plex name vinum0.p0 org concat
> sd name vinum0.p0.s0 drive vinumdrive0 size 0
> sd name vinum0.p0.s1 drive vinumdrive1 size 0
>
>
>
> After trying numerous times to read the drives:
>
> # vinum read /dev/ad2c /dev/ad3c
> Apr 23 13:41:07 slumber /kernel: vinum: no drives found
>
>
> I've even got as far as to redo the configurtion:
>
> vinum create -f /etc/vinum.conf
>
> but i get:
>
>
> 1: drive vinumdrive0 device /dev/ad2c
> ** 1 Can't initialize drive vinumdrive0: Inappropriate ioctl for device
> 2: drive vinumdrive1 device /dev/ad3c
> ** 2 Can't initialize drive vinumdrive1: Inappropriate ioctl for device
>
>
> Both drives are there and seem fine, only other odd behavior is..
>
> su-2.03# disklabel /dev/ad3c
> # /dev/ad3c:
> type: ESDI
> disk: ad3s1
> label:
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 16
> sectors/cylinder: 1008
> cylinders: 59597
> sectors/unit: 60074721
> 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: 60074721 0 vinum # (Cyl. 0 -
> 59597*)
> Warning, partition c is not marked as unused!
> Warning, An incorrect partition c may cause problems for standard system
> utilities
>
>
> This error message appears on both drives. I dont recall seeing this msg
> before when
> I setup vinum, but I also dont think its a bad drive when both started
> doing it at
> the same time.
>
>
> Am i doing something wrong? I've had this working fine for about a year
> now and never had
> problems upgrading, this 4.3 release seems to have broke it but I cant say
> I know why.
>
> I apologize if there is not enough information, i'll be glad to include
> any additional
> information needed. Thanks.
> --
>
> Shawn Ostapuk
> Senior UNIX System Administrator
> Inficad Communications
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
