evice /dev/da1s1e
drive ibmb device /dev/da2s1e
drive ibmc device /dev/da3s1e
volume raid5 setupstate
plex org raid5 512k
sd length 0m drive ibma
sd length 0m drive ibmb
sd length 0m drive ibmc
This works ok. Then I run vinum init to initialize the drives. Trying
to create a filesyst
Greg 'groggy' Lehey writes:
> You don't say whether you're using vinum or gvinum. I've never seen
> this problem before, but if you're getting incorrect subdisk sizes,
> try specifying them explicitly:
>
> sd length 35840952s drive ibma
>
On Monday, 6 December 2004 at 0:28:01 +0100, Markus Hoenicka wrote:
> Hi all,
>
> I'm trying to set up vinum on a freshly installed FreeBSD 5.3-BETA7
> box. The system is installed on da0. I want to use three 18G SCSI
> drives to create a vinum volume.
>
> For some
Hi all,
I'm trying to set up vinum on a freshly installed FreeBSD 5.3-BETA7
box. The system is installed on da0. I want to use three 18G SCSI
drives to create a vinum volume.
For some reason vinum believes the disks hold a mere 255MB. This is
what vinum sets the subdisk length if I specif
I was trying to test my ability to recover from a disk
crash and managed to toast my system disk. Therefore,
I do not have any relevant vinum history file or
messages file.
What happened is that I purposely blew away the drive
named ahc0t15, and was trying to recover it.
In error, I ran the
On Wednesday, 24 November 2004 at 15:10:47 +0800, Rene C. Mendoza wrote:
> Hi!
>
> I'm supposed to mirror 2 similar disk drives using FreeBSD 5.3 The
> thing is, I am confused which utility to use: vinum, gvinum, or geom.
> As I understand it, geom is still fairly new but v
Hi!
I'm supposed to mirror 2 similar disk drives using FreeBSD 5.3 The
thing is, I am confused which utility to use: vinum, gvinum, or geom.
As I understand it, geom is still fairly new but very promising.
Vinum, on the other hand, seems to be stable but not as extensible as
geom. G
Hello,
I just had a "power outtage" (= i accidentally hit the killswitch on the
master power source...). One of the machines affected was one running FreeBSD
with several vinum volumes[1].
When booting up afterwards, all but one of the vinum volumes recovered
completely. By &quo
Hello.
Got a couple of server with vinum mirrored volumes. From time to time a
disk or the other tends to get out of sync and is labeled as stale.
If I miss the thing in the logs it might stay so for months...
The ideal solution would be to write a script to include vinum status in
the daily
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 21 November 2004 14:36, Александр Деревянко wrote:
[...]
> From my point of view, vinum root partition is really useless. You will
> never have the availability comparable to hardware RAID (i mean,
> downtime), and will have
Chris Smith wrote:
Hi,
I've just built a machine with a vinum root successfully. All vinum
sets show that they are up and working. There are two ATA disks in a
RAID1 root formation.
Some questions?
1. The set has just failed completely (sorry it isn't up and working
now) on the first r
don't think you can boot off a vinum partition, because you have to
> load vinum *after* the kernel is running. It usually loads early during
> the run through /etc/rc as the system goes multiuser, before visiting
> /etc/fstab with mount. Perhaps you have your root partition on another
>
On Tue, 2004-11-16 at 08:51, Chris Smith wrote:
[snip]
> ... Can you boot off a striped volume and will it
> benefit me at all making it a striped volume at all rather than a
> concat?
I don't think you can boot off a vinum partition, because you have to
load vinum *after* the ker
On Tuesday, 16 November 2004 at 18:51:38 +, Chris Smith wrote:
> Hi,
>
> I've just built a machine with a vinum root successfully. All vinum
> sets show that they are up and working. There are two ATA disks in a
> RAID1 root formation.
>
> Some questions?
Ho
Hi,
I've just built a machine with a vinum root successfully. All vinum
sets show that they are up and working. There are two ATA disks in a
RAID1 root formation.
Some questions?
1. The set has just failed completely (sorry it isn't up and working
now) on the first reboot. It is p
I have two vinum volumes on my system; one, a mirrored volume, is /usr,
and the other is mounted to /usr/storage.
After updating to 5.3-RELEASE, boot into multi-user mode fails with a
dangling vnode panic.
According to the Errata:
(31 Oct 2004, updated on 12 Nov 2004) The vinum(4) subsystem
On Thu, 11 Nov 2004, Artem Kazakov wrote:
Tom Przybylinski wrote:
Would someone be so kind as to point me at a HOWTO
where I can RTFM on moving my /usr to a freshly
vinum'd stripey vol?
now either dump /usr or tar it and then restore or untar consequently.
If you choose tar do the following:
tar -
[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 m
ot of 'classic' vinum functionality is still missing and
at least for me it still doesn't do the job the way I would find
trustworthy. See below.
That's absolutely true. While 5.3 is IMHO pretty stable, gvinum is quite new
and therefore a bit less well tested than the rest of the s
ong
> way to go. A lot of 'classic' vinum functionality is still missing and
> at least for me it still doesn't do the job the way I would find
> trustworthy. See below.
That's absolutely true. While 5.3 is IMHO pretty stable, gvinum is quite new
and therefore a bit les
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 a
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
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 i
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 ca
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:
>
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
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
Tom Przybylinski wrote:
Salutations list,
Would someone be so kind as to point me at a HOWTO
where I can RTFM on moving my /usr to a freshly
vinum'd stripey vol?
It's pretty easy.
First, you have to create vinum volume, for example you name it "stripe"
(read vinum docs to fin
Salutations list,
Would someone be so kind as to point me at a HOWTO
where I can RTFM on moving my /usr to a freshly
vinum'd stripey vol?
TIA,
Tom
__
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
__
I have an absurd problem with vinum. I use the following command:
vinum create blob.conf
blob.conf:
drive d1 device /dev/ad4s1d
drive d2 device /dev/ad5s1d
drive d3 device /dev/ad6s1d
drive d4 device /dev/ad7s1d
volume blob
plex org raid5 433k
sd length 0 drive d1
sd length 0 drive d2
On Monday, 8 November 2004 at 1:01:04 -0600, matt virus wrote:
> Hi All -
>
> with some help from people on this list, i managed to get vinum and
> raid5 all figured out!
>
> I had 4 * 160gb raid5 array running perfectly. When i ventured home
> this past weekend, i found a
On 07 nov 2004, at 00:19, Greg 'groggy' Lehey wrote:
On Sunday, 31 October 2004 at 14:03:18 +0100, FreeBSD questions
mailing list wrote:
On 31 okt 2004, at 07:41, matt virus wrote:
matt virus wrote:
Hi all!
I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
array
42300
matt virus wrote:
Hi All -
with some help from people on this list, i managed to get vinum and
raid5 all figured out!
I had 4 * 160gb raid5 array running perfectly. When i ventured home
this past weekend, i found another ATA controller and figured I'd
change my raid5 array to have 8 dri
Hi All -
with some help from people on this list, i managed to get vinum and
raid5 all figured out!
I had 4 * 160gb raid5 array running perfectly. When i ventured home
this past weekend, i found another ATA controller and figured I'd change
my raid5 array to have 8 drives.
I cleane
On Sunday, 31 October 2004 at 14:03:18 +0100, FreeBSD questions mailing list
wrote:
>
> On 31 okt 2004, at 07:41, matt virus wrote:
>
>> matt virus wrote:
>>> Hi all!
>>> I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
>>> array
On 31 okt 2004, at 07:41, matt virus wrote:
nobody ???
OK I'll give it a try. I have a vinum RAID 1 running though, but the
way to get it tunning isn't very different.
matt virus wrote:
Hi all!
I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
array with.
the device
nobody ???
matt virus wrote:
Hi all!
I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
array with.
the devices are:
ad4ad11
All drives have been fdisk'd and such,
ad4s1d.ad11s1d
The first step of setting up vinum is changing the disklabel
disklabel -e /dev/ad
"h0444lp6" <[EMAIL PROTECTED]> wrote:
> Dear list,
>
> I do wonder a little about the difference in the size for my
> /dev/vinum/usr reported by ¡§vinum list¡¨ and ¡§df ¡Vh¡¨.
> I concatenated three 1303MB partitions. "vinum list" shows as expected a
&
Dear list,
I do wonder a little about the difference in the size for my
/dev/vinum/usr reported by “vinum list” and “df –h”.
I concatenated three 1303MB partitions. "vinum list" shows as expected a
size of 3909MB for volume usr, but df -h shows me only the size 1303MB.
Why?
TIA
zhey
Hi all!
I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
array with.
the devices are:
ad4ad11
All drives have been fdisk'd and such,
ad4s1d.ad11s1d
The first step of setting up vinum is changing the disklabel
disklabel -e /dev/ad4
The disk label says it
This is what happend...
Still got the second disk... what to do now?
Fsck -b32 -y /dev/vinum/mirror
webserver1# mount /dev/vinum/mirror /a
webserver1# ls
.cshrc .login_conf .mailrc .rhosts
.login .mail_aliases .profile.shrc
webserver1# cd /a
Have a vinum setup... two disk...
Vinum.conf
drive d1 device /dev/ad2s1e
drive d2 device /dev/ad3s1e
volume mirror
plex org concat
sd length 19m drive d1
plex org concat
sd length 19m drive d2
when I try to run fsck /dev/vinum
: +45 8677 0615
-Oprindelig meddelelse-
Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] På vegne af Erik Udo
Sendt: 23. oktober 2004 12:49
Til: [EMAIL PROTECTED]
Emne: Re: SV: SV: Vinum, and poweroutage...
I dont know, i'm not that expert on disk recovering.
Thomas Rasmussen wrote:
I dont know, i'm not that expert on disk recovering.
Thomas Rasmussen wrote:
Ok... but should i try the local disk thing first?..
How to check the disk it self?
But with a vinum part... are you able to remove the second disk... disklabel the disk
and then mount it?
Med venlig hilsen/Best re
Ok... but should i try the local disk thing first?..
How to check the disk it self?
But with a vinum part... are you able to remove the second disk... disklabel the disk
and then mount it?
Med venlig hilsen/Best regards
Thomas Rasmussuen
Network manager, NM Net ApS
Email: [EMAIL PROTECTED
Dunno. Upgrade to 4.10?
Thomas Rasmussen wrote:
Well fsck_ufs is not in freebsd 4.8
What to do?
On Friday 22 October 2004 15:23, Thomas Rasmussen wrote:
Have a vinum setup... two disk...
when I try to run fsck /dev/vinum/mirror
it outputs..
BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH
Well fsck_ufs is not in freebsd 4.8
What to do?
On Friday 22 October 2004 15:23, Thomas Rasmussen wrote:
> Have a vinum setup... two disk...
> when I try to run fsck /dev/vinum/mirror
>
> it outputs..
>
> BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
&g
Get this messages...
webserver1# fsck /dev/ad2s1e
** /dev/ad2s1e
BAD SUPER BLOCK: MAGIC NUMBER WRONG
/dev/ad2s1e: NOT LABELED AS A BSD FILE SYSTEM (vinum)
Med venlig hilsen/Best regards
Thomas Rasmussuen
Network manager, NM Net ApS
Email: [EMAIL PROTECTED]
Tlf./Phone: +45 8677 0606 Fax: +45 8677
. oktober 2004 11:21
Til: [EMAIL PROTECTED]
Emne: Re: SV: SV: Vinum, and poweroutage... HELP!
Try fsck -y /dev/ad0s1? first, i think that should fix it.
Ofcourse you dont need to make it write anything on the disk, just
see what fsck want's to do.
Thomas Rasmussen wrote:
>Do you know why
e: SV: Vinum, and poweroutage... HELP!
I dont think CLEAR will remove any files, it would say something like:
REMOVE? y/n
If it needed to remove files. Anyway, run fsck -y first so that it does
not
write anything, and you'll see if it wants to remove anything.
Thomas Rasmussen wrote:
Because i
PROTECTED] [mailto:[EMAIL PROTECTED] På vegne af Erik Udo
Sendt: 23. oktober 2004 11:07
Til: [EMAIL PROTECTED]
Emne: Re: Vinum, and poweroutage... HELP!
Why didn't you answer "yes" to fsck? I dont think it would have removed
anything...
Few keywords you might want to check:
scan_ffs
-Oprindelig meddelelse-
Fra: Erik Udo [mailto:[EMAIL PROTECTED]
Sendt: 23. oktober 2004 11:12
Til: Thomas Rasmussen
Emne: Re: SV: Vinum, and poweroutage... HELP!
I dont think CLEAR will remove any files, it would say something like:
REMOVE? y/n
If it needed to remove files. Anyway, run fsck -y first so
0615
-Oprindelig meddelelse-
Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] På vegne af Erik Udo
Sendt: 23. oktober 2004 11:07
Til: [EMAIL PROTECTED]
Emne: Re: Vinum, and poweroutage... HELP!
Why didn't you answer "yes" to fsck? I dont think it would have removed
anything.
Why didn't you answer "yes" to fsck? I dont think it would have removed
anything...
Few keywords you might want to check:
scan_ffs
fsck_ffs
Thomas Rasmussen wrote:
Have a vinum setup... two disk...
Vinum.conf
drive d1 device /dev/ad2s1e
drive d2 device /dev/ad3s1e
volume mirro
0615
-Oprindelig meddelelse-
Fra: Erik Udo [mailto:[EMAIL PROTECTED]
Sendt: 23. oktober 2004 11:03
Til: Thomas Rasmussen
Emne: Re: Vinum, and poweroutage... HELP!
Why didn't you answer "yes" to fsck? I dont think it would have removed
anything...
Few keywords you might wan
Have a vinum setup... two disk...
Vinum.conf
drive d1 device /dev/ad2s1e
drive d2 device /dev/ad3s1e
volume mirror
plex org concat
sd length 19m drive d1
plex org concat
sd length 19m drive d2
when I try to run fsck /dev/vinum
On 10/20/2004 1:56 PM Henk wrote:
Vinum reported one my disks in the volume has crashed. As mentioned in
the thread
http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/045942.html
I did 2 things.
*snip*
ttyp2 0:21 #kneh# [/home/marc>vinum start
Warning: defective object
> > In /boot/loader.conf I set:
> >
> > vinum_load="YES"
> > vinum.autostart="YES"
> >
> > This doest not work, even:
> >
> > gvinum_load="YES"
> > gvinum.autostart="YES"
> >
> > When i boot in s
16:23
Til: [EMAIL PROTECTED]
Emne: Re: Vinum, and poweroutage...
On Friday 22 October 2004 15:23, Thomas Rasmussen wrote:
> Have a vinum setup... two disk...
> when I try to run fsck /dev/vinum/mirror
>
> it outputs..
>
> BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE W
On Friday 22 October 2004 15:23, Thomas Rasmussen wrote:
> Have a vinum setup... two disk...
> when I try to run fsck /dev/vinum/mirror
>
> it outputs..
>
> BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST
> ALTERNATE
> CANNOT FIGURE OUT FILE SYSTEM P
Have a vinum setup... two disk...
Vinum.conf
drive d1 device /dev/ad2s1e
drive d2 device /dev/ad3s1e
volume mirror
plex org concat
sd length 19m drive d1
plex org concat
sd length 19m drive d2
when I try to run fsck /dev/vinum
. I didn't realize
> > how ready gvinum was for production until I edited my /etc/fstab a couple
> > of weeks ago to replace /dev/vinum with /dev/gvinum and everything Just
> > Worked (tm). Wish all of my software migrations were this easy. :)
> >
I edited my /etc/fstab a couple
> of weeks ago to replace /dev/vinum with /dev/gvinum and everything Just
> Worked (tm). Wish all of my software migrations were this easy. :)
>
> > You can't imagine how happy i am atm. Now i finally can move on.
> >
> > Thanks a
Mark Frasa wrote:
Hello,
I have found this link:
http://www.freebsd.de/archive/de-bsd-questions/de-bsd-questions.200410/0112.html
There is a statement in there:
Ab -- wahrscheinlich so -- 5.5-RELEASE wird vinum komplett durch
(ein formatkompatibles) geom-basiertes Vinum-Framework (g_vinum
Hello,
I have found this link:
http://www.freebsd.de/archive/de-bsd-questions/de-bsd-questions.200410/0112.html
There is a statement in there:
>Ab -- wahrscheinlich so -- 5.5-RELEASE wird vinum komplett durch
>(ein formatkompatibles) geom-basiertes Vinum-Framework (g_vinum) ersetzt
&g
> Vinum reported one my disks in the volume has crashed. As mentioned in
> the thread
> http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/045942.html
> I did 2 things.
*snip*
> ttyp2 0:21 #kneh# [/home/marc>vinum start
> Warning: defective objects
>
> P
[ Stuff deleted ]
Thanks for the pointer - the setupstate keyword did the trick. And my
apologies for not RTFM :) *goes off with burning cheeks*
If you're still interested in the panic output I'll try and find some time
in the near future to try and get hold of it.
Cheers
Dave
I'm currently trying to use vinum to set up a thin client which will
function as a mirroring fileserver. The idea is that the customer will
enable the mirror using a web-interface. But, of course, I'm having
problems. The main one is that for some reason vinum says that one of the
two
Hello,
First i want to quote something:
>Vinum is being rewritten; the new one is called gvinum or geom_vinum.
>
> It handles swap, and it should be in 5.3.
>
> Greg
Here Greg tells me that Vinum should be in 5.3 Yesterday after 5.3-RC1 came trough, i
downloaded the ISO and in
Hello.
I've got a 4.10 server which sometimes reboots itself, so I'd like it to
create crash dumps for me to analize, but, after an upgrade, no swap
partition is big enough to hold its entire RAM. So I tought I could join
two of them with vinum...
Any hint?
Any tutorial?
Any reason
Dear Vinum-know-it-all / Greg:-)
Vinum reported one my disks in the volume has crashed. As mentioned in the thread
http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/045942.html I did 2
things.
1. vinum -> setstate up BigDisk0.p0.s0 BigDisk0.p0
FreeBSD did not like that and deci
ay belong on current,> I upgraded to 5.2 from 5.1 and my
>>>>> kernel (GENERIC) now refuses to use /dev/vinum/swap as my swap
>>>>> device.>> # swapon /dev/vinum/swap> swapon: /dev/vinum/swap:
>>>>> Operation not supported by device> #
reeBSD 5.2.1, because 4.10 and even 5.1 did not
> > reconized mij SATA controller, i CVS-upped and upgraded to 5.2.1-p11
> > RELEASE
> >
> > After that I configured Vinum to mirror (RAID 1) 2 80G Maxtor SATA
> > disks.
> >
> > The error i am getting is:
>
ded to 5.2.1-p11
> RELEASE
>
> After that I configured Vinum to mirror (RAID 1) 2 80G Maxtor SATA
> disks.
>
> The error i am getting is:
>
> swapon /dev/vinum/swap > swapon: /dev/vinum/swap: Operation not
> supported by devi
c:
>
>drive ad5 device /dev/ad5s1e
>drive ad6 device /dev/ad6s1e
>volume raid0
>plex org striped 127k
>sd length 0 drive ad5
>sd length 0 drive ad6
It's a *very* bad idea to name Vinum drives after their current
location. You can take the (physical) dri
Greg 'groggy' Lehey wrote:
On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote:
> Hi Greg and list!
Thank you for your reply!
> I did have two 120 GB's disk drives in vinum as a striped raid.
Can you be more specific?
My vinum.conf looks like this, if this i
On Thursday, 7 October 2004 at 18:11:52 +0200, Paul Everlund wrote:
> Hi Greg and list!
>
> I did have two 120 GB's disk drives in vinum as a striped raid.
Can you be more specific?
> One disk crashed, and is not found during boot. It starts up and
> makes the usual noises
Hi Greg and list!
I did have two 120 GB's disk drives in vinum as a striped raid.
One disk crashed, and is not found during boot. It starts up and
makes the usual noises, but then it stalls with a katjing, katjing
and so on. It seems like either the steering electronics, or the
read/write-
Hello.
I apologize for the mistakes and omissions in my original posting. I've
included additional information in this message.
I'm running Vinum on a Free BSD 4.9 system with 3 hard drives. It's been
operational for about 5 years. The first drive is a small one and I boo
On Tuesday, 5 October 2004 at 7:47:24 -0500, John Souvestre wrote:
> In-Reply-To: <[EMAIL PROTECTED]>
Please don't reply to unrelated threads. See
http://www.lemis.com/questions.html for more details.
> I'm running Vinum on a 4.9 system with 3 drives. The first drive
Hi.
I'm running Vinum on a 4.9 system with 3 drives. The first drive is a small
one and I boot from it. The second and third drive are mirrored, using Vinum,
and contain most of the system's data (1 volume, 1 plex per drive, 1 subdisk
per plex).
The system locked up on me this mornin
Hello questions,
Please include me in replies. I'm running 5.2.1-RELEASE built late
last month and can't get vinum to list it's configuration. Could my
securelevel have something to do with it?
Thanks.
0 tfz /root # vinum printconfig
Can't open /dev/vinum/control: Ope
> drive a device /dev/ad0
> drive b device /dev/ad3
...
> ** 1 Can't initialize drive a: Operation not supported by device
...
> illuminating. Is this a common problem? How do I fix it? I've made
> sure that the disks in question have been labeled using disklabel -e
&
Hello all,
I'm setting up a mirrored volume with vinum, using the following config file:
drive a device /dev/ad0
drive b device /dev/ad3
volume storage
plex org concat
sd length 78167m drive a
plex org concat
sd length 78167m drive b
but when I run the config, I get this:
vinum ->
On Tuesday, 21 September 2004 at 8:24:44 -0500, David Kelly wrote:
>
> On Sep 20, 2004, at 8:52 PM, Greg 'groggy' Lehey wrote:
>
>>> We could not find stated exactly anywhere, but we are presuming the
>>> description file that you use with vinum create become
On Sep 20, 2004, at 8:52 PM, Greg 'groggy' Lehey wrote:
We could not find stated exactly anywhere, but we are presuming the
description file that you use with vinum create becomes
/etc/vinum.conf
Well, you need to call it that. The name isn't critical, but it's a
good choice.
On Tuesday, 21 September 2004 at 9:13:23 +1200, Bruce Harding wrote:
> We are currently trying to set up server with software raid using vinum
> on 5.3. We plan to use it as a Mirrored root filesystem So far we have
> followed Greg Lehey's instructions from
>
> http://www.d
We are currently trying to set up server with software raid using vinum
on 5.3. We plan to use it as a Mirrored root filesystem So far we have
followed Greg Lehey's instructions from
http://www.daemonnews.org/22/vinum.html
and the handbook on vinum:
http://www.freebsd.org/doc/en_US.IS
On Wednesday, 8 September 2004 at 13:13:22 +0200, Thomas Spreng wrote:
> Hi,
>
> I have made concat drive using 3 hard disks using vimum vm. Some weeks
> ago one of those 3 disks crashed completely (bios can't even detect it
> anymore). My question now is: is there any chance to recover the data
>
Hi,
I have made concat drive using 3 hard disks using vimum vm. Some weeks
ago one of those 3 disks crashed completely (bios can't even detect it
anymore). My question now is: is there any chance to recover the data
that resides on the 2 (working) remaining disks?
I cant provide more info than th
hear that it is not correct.
> > While not having heard back yet, I had to rebuild another subdisk,
> > but I decided to do it off-line this time. Turns out the parity was
> > rebuilt ok.
>
> Yes, this is what I recommended.
OK.
> > Might there be a bug in the
On Thursday, 2 September 2004 at 18:12:39 +0200, Feczak Szabolcs wrote:
> Hi
>
> I have the following concatenated array:
>
> 3 drives:
> D vinumdrive0 State: up /dev/ad2A: 0/152627 MB (0%)
> D vinumdrive1 State: up /dev/ad3A: 0/152627 MB (0%)
> D vi
On Thursday, 2 September 2004 at 12:17:01 +0200, Stijn Hoop wrote:
> Hi,
>
> back with another episode in this continuing saga:
>
> On Sun, Aug 29, 2004 at 04:26:57PM +0200, Stijn Hoop wrote:
>> Witness this (after yet another fake disk crash):
>>
>>>>>
&
e vinum.drives setting). Vinum.autostart just tells
> 5.x to run the discovery code.
Addition: the code to parse the name of the root device in 4.x is too
narrow-minded to parse a string like /dev/vinum/root, it can only
parse [/dev/]DDU[sS]P-style root device names (DD - driver name, U -
unit num
.
Segmentation fault (core dumped)
fsck says
BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE
/dev/vinum/vol: CANNOT FIGURE OUT FILE SYSTEM PARTITION
any ideas to solve it ?
--
_(_)_
(_. o_)F3CZ0
(_,) http://feczo.nmi.rulez.org
ob
On Thu, 2004-09-02 at 02:34, FreeBSD Daemon wrote:
> Dear list,
>
> I am using 4.10R and want to set up a mirrored / using vinum.
>
> I am confused by the note in section 17.9.1 of the handbook stating that
> the following paragraphs only apply to 5.x and refer to 17
Hi,
back with another episode in this continuing saga:
On Sun, Aug 29, 2004 at 04:26:57PM +0200, Stijn Hoop wrote:
> Witness this (after yet another fake disk crash):
>
> %%%
>
> vinum -> ls -v local.p0.s0
> Subdisk local.p0.s0:
> Size: 314
Dear list,
I am using 4.10R and want to set up a mirrored / using vinum.
I am confused by the note in section 17.9.1 of the handbook stating that
the following paragraphs only apply to 5.x and refer to 17.9.5 for 4.x
configuration.
Do I have to set just vinum_load, vinum.drives, and
I'm working on setting up a mirrored root filesystem as explained in:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html
I've gotten it to boot then noticed something broken about it on my setup.
More info on my setup is at the bottom of this message.
If it bo
and the parity on the other disks.
> >
> > Yes, but the parity should be recalculated at the same time, right?
>
> Yes.
Witness this (after yet another fake disk crash):
%%%
vinum -> ls -v local.p0.s0
Subdisk local.p0.s0:
Size: 31457129472 bytes (2 MB
201 - 300 of 951 matches
Mail list logo
