Modulok wrote:
> Take the following example vinum config file:
>
> drive a device /dev/da2a
> drive b device /dev/da3a
>
> volume rambo
> plex org concat
> sd length 512m drive a
> plex org concat
> sd length 512m drive b
>
8
t;, "disparity"? I could use trial and error, but there has
to be a document with this information somewhere. Other than rummaging
through source code, is there any additional documentation on vinum
configuration syntax, (A strict specification would be great!)? I
found a FreeBSD Diary articl
[Format recovered--see http://www.lemis.com/email/email-format.html]
Text wrapped.
On Thursday, 11 November 2004 at 12:00:52 +0200, Kim Helenius wrote:
> Greetings. I posted earlier about problems with vinum raid5 but it
> appears it's not restricted to that:
>
> Let's make a fresh start with vin
Stijn Hoop wrote:
Hi,
On Thu, Nov 11, 2004 at 04:53:39PM +0200, Kim Helenius wrote:
Stijn Hoop wrote:
I don't know the state of affairs for 5.2.1-RELEASE, but in 5.3-RELEASE
gvinum is the way forward.
Thanks again for answering. Agreed, but there still seems to be a long
way to go. A lot of 'clas
Hi,
On Thu, Nov 11, 2004 at 04:53:39PM +0200, Kim Helenius wrote:
> Stijn Hoop wrote:
> > I don't know the state of affairs for 5.2.1-RELEASE, but in 5.3-RELEASE
> > gvinum is the way forward.
>
> Thanks again for answering. Agreed, but there still seems to be a long
> way to go. A lot of 'clas
Stijn Hoop wrote:
Greetings. I posted earlier about problems with vinum raid5 but it
appears it's not restricted to that.
Are you running regular vinum on 5.x? It is known broken. Please use
'gvinum' instead.
There is one caveat: the gvinum that shipped with 5.3-RELEASE contains an
error in RAID-5
On Thu, Nov 11, 2004 at 03:32:58PM +0200, Kim Helenius wrote:
> On Thu, 11 Nov 2004, Stijn Hoop wrote:
> > On Thu, Nov 11, 2004 at 12:00:52PM +0200, Kim Helenius wrote:
> > > Greetings. I posted earlier about problems with vinum raid5 but it
> > > appears it's not restricted to that.
> >
> > Are
On Thu, 11 Nov 2004, Stijn Hoop wrote:
> On Thu, Nov 11, 2004 at 12:00:52PM +0200, Kim Helenius wrote:
> > Greetings. I posted earlier about problems with vinum raid5 but it
> > appears it's not restricted to that.
>
> Are you running regular vinum on 5.x? It is known broken. Please use
> 'gvinu
On Thu, Nov 11, 2004 at 12:00:52PM +0200, Kim Helenius wrote:
> Greetings. I posted earlier about problems with vinum raid5 but it
> appears it's not restricted to that.
Are you running regular vinum on 5.x? It is known broken. Please use
'gvinum' instead.
There is one caveat: the gvinum that sh
On Thu, 11 Nov 2004, Artem Kazakov wrote:
> Kim Helenius wrote:
>
> > Now I can newfs /dev/vinum/vinum0, mount it, use it, etc. But when I do
> > vinum stop, vinum start, vinum stop, and vinum start something amazing
> > happens. Vinum l after this is as follows:
> >
> > 2 drives:
> > D d2
Kim Helenius wrote:
Now I can newfs /dev/vinum/vinum0, mount it, use it, etc. But when I do
vinum stop, vinum start, vinum stop, and vinum start something amazing
happens. Vinum l after this is as follows:
2 drives:
D d2State: up /dev/ad5s1d A: 286181/286181
MB (10
Greetings. I posted earlier about problems with vinum raid5 but it
appears it's not restricted to that:
Let's make a fresh start with vinum resetconfig. Then vinum create
kala.txt which contains:
drive d1 device /dev/ad4s1d
drive d2 device /dev/ad5s1d
volume vinum0
plex org concat
sd length 586
On Friday, 27 February 2004 at 14:06:48 -0500, Jason Schadel wrote:
> Here's my situation. I have two machines. One running OpenBSD on a
> 60gig drive and one running FreeBSD on a 10gig drive with a second 60gig
> for storage. I want to take the 60 gig drive from the OpenBSD box and
> use it as
Here's my situation. I have two machines. One running OpenBSD on a
60gig drive and one running FreeBSD on a 10gig drive with a second 60gig
for storage. I want to take the 60 gig drive from the OpenBSD box and
use it as a mirror to the 60 gig in the FreeBSD box. The catch is I
want to creat
On Sunday, 23 November 2003 at 19:15:30 -0500, dave wrote:
> Hello,
> Trying to get vinum going on a 5.1 machine, with two IDE 40 gb hard
> drives at the moment, two more will be added later once i know my setup is
> working. Below are my disklabels for ad0s1 and ad1s1 as well
Hello,
Trying to get vinum going on a 5.1 machine, with two IDE 40 gb hard
drives at the moment, two more will be added later once i know my setup is
working. Below are my disklabels for ad0s1 and ad1s1 as well as the vinum
configuration. I need to know if all of this is right and if not what
On Fri, Nov 21, 2003 at 04:43:53PM +0200, Jani Reinikainen wrote:
> I added another spindle for this setup, I just thought debugging one
> spindle's setup at a time would be easier. Now my RAID-1 is complete
> and working.
I guessed as much but my reply wouldn't have been complete without the
obli
On Thu, 20 Nov 2003 10:56:40 +
Lewis Thompson <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 20, 2003 at 11:53:52AM +0200, Jani Reinikainen wrote:
> > Created a new partition 'h':
> > - size = 12715857 ('c' partition) - 265 = 12715592
> > - offset 16
>
> Why isn't that:
>
> - size = 12715857 ('c'
On Thu, Nov 20, 2003 at 11:53:52AM +0200, Jani Reinikainen wrote:
> Created a new partition 'h':
> - size = 12715857 ('c' partition) - 265 = 12715592
> - offset 16
Why isn't that:
- size = 12715857 ('c' partition) - 16 = 12715841
- offset 16?
I'm no Vinum guru but afaik the 265 at the beginnin
Greetings,
I'm trying to setup Vinum on a FreeBSD 5.1-RELEASE box, according to the
instructions at http://www.vinumvm.org/cfbsd/vinum.txt, pages 236-240,
where the idea is to create one big Vinum partition which overlaps all
other partitions.
Basically, what I've done so far:
In disklabel, crea
export.p0 S State: up Subdisks: 0 Size: 0 B
-1 subdisks:
- Original Message -
From: "lukek" <[EMAIL PROTECTED]>
To: "FreeBSD" <[EMAIL PROTECTED]>
Sent: 2003年8月21日 9:34
Subject: Vinu
Hello,
I am having a bit of trouble getting the conf file correct. I have listed
the devices and slice names but get the following error
vinum -> create -f vinum.conf
1: drive d1 /dev/ad1s1e
** 1 Drive d1, invalid keyword: /dev/ad1s1e: Invalid argument
2: drive d2 /dev/a
0unused0 0# (Cyl.0 - 9964*)
> e: 160086528 0 vinum # (Cyl.0 - 9964*)
OK.
> Here's my vinum configuration file (/etc/vinum.conf):
Not needed.
> Here's the output of `vinum list' after doing `vinum create
disks were configured as
"dangerously dedicated" (using /stand/sysinstall).
Here's the output of `fdisk ad2':
Here's my vinum configuration file (/etc/vinum.conf):
drive d1 device /dev/ad2s1e
drive d2 device /dev/ad4s1e
drive d3 device /dev/ad6s1e
drive d4 device /dev/ad8s1e
0 # milliseconds
drivedata: 0
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
c: 1600865280unused0 0# (Cyl.0 -
9964*)
e: 1600865280 vinum # (Cyl. 0 -
9964*)
Here's my vinum configuration file (/e
25 matches
Mail list logo
