From owner-freebsd-questions@FreeBSD.ORG Mon Dec 22 12:34:13 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3B9F16A4CE for ; Mon, 22 Dec 2003 12:34:13 -0800 (PST) Received: from Raffles-IT.com (raffles.demon.co.uk [62.49.18.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0A0243D1F for ; Mon, 22 Dec 2003 12:34:05 -0800 (PST) (envelope-from dpd@Raffles-IT.com) Received: from arrow.lan.raffles-it.com (localhost [127.0.0.1]) hBKGWTll017005 for ; Sat, 20 Dec 2003 16:32:29 GMT (envelope-from dpd@lan.raffles-it.com) Received: (from dpd@localhost)hBKGWT64017004; Sat, 20 Dec 2003 16:32:29 GMT (envelope-from dpd) Date: Sat, 20 Dec 2003 16:32:28 +0000 From: David Dooley To: freebsd-questions@freebsd.org Message-Id: <20031220163228.3fb3e493.dpd@raffles-it.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on arrow.lan.raffles-it.com Subject: Vinum and Promise ATS Raid card X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2003 20:34:14 -0000 Hi I am having a problems creating vinum objects. I have 4 200GB disks connected to a Promise ATA FastTRAK raid controller and the disk are defined as a 400GB Raid 0+1 drive. This all appears to be fine and is viasable to the OS ar0: 381469MB [48630/255/63] status: READY subdisks: 0 READY ad0: 190782MB [387621/16/63] at ata2-master UDMA100 1 READY ad1: 190782MB [387621/16/63] at ata2-slave UDMA100 2 READY ad2: 190782MB [387621/16/63] at ata3-master UDMA100 3 READY ad3: 190782MB [387621/16/63] at ata3-slave UDMA100 As that stands I can label the disk and newfs it and all is working fine. # /dev/ar0c: type: ESDI disk: ar0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 48629 sectors/unit: 781240887 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: 781240887 0 unused 0 0 # (Cyl. 0 - 48629*) e: 781240887 0 4.2BSD 2048 16384 89 # (Cyl. 0 - 48629*) and after newfs with the file system mounted Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ar0e 384514280 2 353753136 0% /mnt Now what I would really like to do is is create lots of vinum objects that I can use to create file systems out of and to extend them as and when needed and also to remove the whole 7 partitions limitation. So after unmounting the file system and changeing the disk label to from 4.2BSD to vinum # disklabel -r ar0 # /dev/ar0c: type: ESDI disk: ar0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 48629 sectors/unit: 781240887 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: 781240887 0 unused 0 0 # (Cyl. 0 - 48629*) e: 781240887 0 vinum # (Cyl. 0 - 48629*) I tried to do the first step in creating a vinum volume si I created a config file with the line drive a device /dev/ar0e I then fired up vinum and ran the command vinum -> create -f /etc/vinum.config and got the response 1: drive a device /dev/ar0e ** 1 Can't initialize drive a: Operation not supported by device 0 drives: 0 volumes: 0 plexes: 0 subdisks: I tried the config with drive a device /dev/ar0s1e and got the same response can any one tell me if vinum supports hardware raid disks. I really want to use vinum to get of the limitation of 7 file system / partitions per drive so I can create a number of small volumes and add plexes as and when require to grow the file system and not for the redundancy/resiliency aspects as that is taken care of by the hardware. Thanks for any help and advice. David. -- David Dooley dpd@raffles-it.com