Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Oct 2000 15:32:07 -0800
From:      Alfred Perlstein <bright@wintelcom.net>
To:        gdunn@mac.com
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Help With Vinum Syntax
Message-ID:  <20001031153207.G22110@fw.wintelcom.net>
In-Reply-To: <00103113292800.04686@shf102107.hi.pac.army.mil>; from gdunng@mac.com on Tue, Oct 31, 2000 at 01:14:52PM -1000
References:  <00103113292800.04686@shf102107.hi.pac.army.mil>

next in thread | previous in thread | raw e-mail | index | archive | help
* Gary Dunn <gdunng@mac.com> [001031 15:28] wrote:
> 
> =-=-=-=-=
> 
> Stuck in vinum setup, Invalid argument error.
>   
>  FreeBSD 4.1 as server
>  Two SCSI hard drives, da0 and da1
>  Goal: - root, usr, small windows share on da0
>        - apache web content on da1
>        - mirrored volume for user mail storage
>   
>  Output of df:
>   
>  Filesystem	1K-blocks	Used	Avail	Capacity	Mounted on
>  /dev/da0s2a	49583      	26940	18677	    59%  /
>  /dev/da0s3e  	4359077        	1  	4010350    0%    /p0
>  /dev/da1s1e  	4359077        	1  	4010350    0%    /p1

--^^^^^^^^^^^ ummm...

>  /dev/da0s2f  	1348443  	123768	1116800    10%    /usr
>  /dev/da0s2e    	19815      	242	17988        1%    /var
>  /dev/da0s4e  	2280928        	1  	2098453    0%    /win
>  /dev/da1s2e  	4242621        	1  	3903211    0%    /www
>  procfs              	4        		4        0  100%    	/proc
>   
>  Vinum configuration file (vinumcfg):
>   
>  drive a device /dev/da0s3e
>  drive b device /dev/da1s1e
>  volume profiles
>    plex org concat
>      sd length 4g drive a
>    plex org concat
>      sd length 4g drive b
>   

using an already mounted filesystem to back a raid setup is a BAD idea.

>   
>  vinum -> create vinumcfg
>    1: drive a device /dev/da0s3e
>  ** 1 : Invalid argument
>    2: drive b device /dev/da1s1e
>  ** 2 : Invalid argument

of course, they're mounted and not fstype 'vinum' which the manpage
explains:

   DRIVE LAYOUT CONSIDERATIONS
     vinum drives are currently BSD disk partitions.  They must be of type
     vinum in order to avoid overwriting data used for other purposes.  Use
     disklabel -e to edit a partition type definition.  The following display
     shows a typical partition layout as shown by disklabel:

...

-Alfred



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?20001031153207.G22110>