r time the
fundamental assumptions that a piece of code makes are tested as the
interfaces and subsystems it depends on evolve and change. These
assumptions can be very subtle sometimes, and difficult to find and
test.
Vinum is hard to test because it requires multiple disks to test
with. In additi
Poul-Henning Kamp wrote:
> With Greg being a core@ member, and well known for his ability to
> talk an acturan megadonkey into taking a stroll after first having
> talked its legs off about procedural issues, "Doing something about
> vinum" is permanently on the "we
On Thursday, 27 November 2003 at 0:13:09 -0600, Cosmin Stroe wrote:
> On Thu, 27 Nov 2003, Greg 'groggy' Lehey wrote:
>
>> On Wednesday, 26 November 2003 at 12:04:52 -0600, Cosmin Stroe wrote:
>>>
>>> I am using vinum atm, and I am having serious prob
On Thu, 27 Nov 2003, Greg 'groggy' Lehey wrote:
> On Wednesday, 26 November 2003 at 12:04:52 -0600, Cosmin Stroe wrote:
> >
> > I am using vinum atm, and I am having serious problems with it. After
> > about 16 hrs of writing data to a vinum volume via NFS at a c
On Wednesday, 26 November 2003 at 12:04:52 -0600, Cosmin Stroe wrote:
>
> I am using vinum atm, and I am having serious problems with it. After
> about 16 hrs of writing data to a vinum volume via NFS at a constant data
> stream of 200k/sec and reading at 400k/sec at the same tim
.
> >Rather than an unproductive public RANT I thought I'd ask for private assistance.
> >I can post a summary afterwards if you like, or even better write a better
> >FAQ/tutorial on vinum.
>
> Joel,
>
> The problem is that vinum is hot political potato in the
for private assistance.
>I can post a summary afterwards if you like, or even better write a better
>FAQ/tutorial on vinum.
Joel,
The problem is that vinum is hot political potato in the project.
In the eyes of a fair number of competent people, vinum has never
quite "made it".
Geeze! Not only aren't there any emails, but I've started a full blown thread!
--On Tuesday, November 25, 2003 8:39 AM -0800 "Joel M. Baldwin" <[EMAIL PROTECTED]> wrote:
Could a vinum guru please contact me via email?
I've lost 2 vinum volumes as a result of the
>> Could a vinum guru please contact me via email?
>>
>> I've lost 2 vinum volumes as a result of the latest fiasco and naturally
>> am eager to figure out what's going on and recover the data.
EA> This isn't necessarily directed at you - I'm just
On Tuesday, 25 November 2003 at 10:48:44 -0600, Eric Anderson wrote:
>
>> Could a vinum guru please contact me via email?
>>
>> I've lost 2 vinum volumes as a result of the latest fiasco and naturally
>> am eager to figure out what's going on and recover
Could a vinum guru please contact me via email?
I've lost 2 vinum volumes as a result of the latest fiasco and naturally
am eager to figure out what's going on and recover the data.
This isn't necessarily directed at you - I'm just using this email as a
footstep to send
Could a vinum guru please contact me via email?
I've lost 2 vinum volumes as a result of the latest fiasco and naturally
am eager to figure out what's going on and recover the data.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.o
On Sunday 23 November 2003 23:50, you wrote:
>
> Yes. The fix wasn't enough. I was holding off committing until I
> could test it.
Thanks for YOUR commit! :-) All works fine here now...
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
_
On Sunday, 23 November 2003 at 22:46:30 +0100, Matthias Schuendehuette wrote:
> Hello,
>
> I just built a new world+kernel after the commit of grogs corrections
> but I still get:
>
> [EMAIL PROTECTED] - ~
> 503 # vinum start
> ** no drives found: No such file or directo
Hello,
I just built a new world+kernel after the commit of grogs corrections
but I still get:
[EMAIL PROTECTED] - ~
503 # vinum start
** no drives found: No such file or directory
--
Ciao/BSD - Matthias
Matthias Schuendehuette , Berlin (Germany)
PGP-Key at and ID: 0xDDFB0A5F
Hi Greg,
On Sat, Nov 22, 2003 at 11:05:38AM +1030, Greg 'groggy' Lehey wrote:
> On Friday, 21 November 2003 at 15:42:12 -0800, Marcus Reid wrote:
> > Hello,
> >
> > I just upgraded a -CURRENT box this afternoon to discover that vinum
> > is broken. If I
On Friday, 21 November 2003 at 15:42:12 -0800, Marcus Reid wrote:
> Hello,
>
> I just upgraded a -CURRENT box this afternoon to discover that vinum
> is broken. If I hadn't done dumps of my working world beforehand I
> would be in pretty sad shape. Should UPDATING make note of
Hello,
I just upgraded a -CURRENT box this afternoon to discover that vinum
is broken. If I hadn't done dumps of my working world beforehand I
would be in pretty sad shape. Should UPDATING make note of this breakage?
It would have saved me some embarassment, and I'm sure others ar
holt wrote:
>
> > I'm getting the same (no
> drives/subdisks/plexes/volumes found) trying to
> > upgrade from a Nov 11 kernel/userland to Nov 16th
> kernel. I tried
> > seeing if using a Nov 16th vinum binary would load
> them, but after doing
> > a stop/st
On Fri, 17 Jan 2003, Eric Anholt wrote:
> I'm getting the same (no drives/subdisks/plexes/volumes found) trying to
> upgrade from a Nov 11 kernel/userland to Nov 16th kernel. I tried
> seeing if using a Nov 16th vinum binary would load them, but after doing
> a stop/start, t
On Sun, 2003-11-16 at 20:14, Daryl Chance wrote:
> I am currently not able to load my vinum array
> (haven't tried to revert back to pre-statfs source)
> after I built a new kernel and world. I upgraded the
> recommended way (installkernel, reboot, single user
> mode, install
At Sun, 16 Nov 2003 20:14:24 -0800 (PST),
Daryl Chance wrote:
> I am currently not able to load my vinum array
> (haven't tried to revert back to pre-statfs source)
Me too.
After upgrading the kernel from -current as of mid september to
today's, I rebooted and got "vinum lo
I am currently not able to load my vinum array
(haven't tried to revert back to pre-statfs source)
after I built a new kernel and world. I upgraded the
recommended way (installkernel, reboot, single user
mode, installworld, etc) and when my box boots I get
"vinum loaded, no drives found
Hello,
On 13.11.2003 at 16:33 cosmin wrote:
Hello, I'm having major problems with the latest kernel sources and
vinum. I don't really know where to begin the debug. For now, I'll
have to run older sources just to have vinum working.
Vinum isn't able to detect my vo
Hello, I'm having major problems with the latest kernel sources and vinum. I don't
really know where to begin the debug. For now, I'll have to run older sources just to
have vinum working.
Vinum isn't able to detect my volume, even though it worked fine before the install
On Monday, Oct 20, 2003, at 19:02 Europe/Budapest, Alexander Leidinger
wrote:
Greg 'groggy' Lehey schrieb:
Provide a dump? Analyse the problem yourself? This *is* -CURRENT,
after all.
I can reproduce this here (same MB). I don't think it's a vinum
problem,
but vinum seems
Greg 'groggy' Lehey schrieb:
Provide a dump? Analyse the problem yourself? This *is* -CURRENT,
after all.
I can reproduce this here (same MB). I don't think it's a vinum problem,
but vinum seems to be a good way to reproduce the bug. I set up a stripe
over 2 SATA
Hi,
I'm trying to setup vinum on 2 identical 30G HD's.
The MB I'm using has a built in Raid 0 controller, so
i have 6 ATA Slots. My Main HD is hooked up to the
primary non-raid. and the other 2 are hooked up to
primary 1 and primary 2 on the raid. I can get vinum
up and runn
On Wednesday, Oct 15, 2003, at 10:34 Europe/Budapest, Soren Schmidt
wrote:
First loose vinum from the mix, if we should have a chance finding
the problem we need to lower the number of unknowns. Then tell us
if and how it fails, dmesg from verbose booted system, backtrace
etc, you know the drill
It seems Balazs Nagy wrote:
> Hi,
>
> I had a -CURRENT setting with an Abit BE7-S and two SATA disks with
> vinum configuration. It worked very well until a power failure, and
> the mainboard died. Yesterday I got a replacement mainboard, the only
> type met the requirem
ile
system from the underlying UFS partition, thus disabling Vinum; at
least that would help you track down the problem.
It has ICH5R south bridge, with correct PCI ids. Film at 11, or when I
go home to generate some crash dump.
--
jul
___
[EMAIL
On Tuesday, 14 October 2003 at 18:46:44 +0200, Balazs Nagy wrote:
> Hi,
>
> I had a -CURRENT setting with an Abit BE7-S and two SATA disks with
> vinum configuration. It worked very well until a power failure, and
> the mainboard died. Yesterday I got a replacement mainboard, the
Hi,
I had a -CURRENT setting with an Abit BE7-S and two SATA disks with
vinum configuration. It worked very well until a power failure, and
the mainboard died. Yesterday I got a replacement mainboard, the only
type met the requirements (eg. two SATA ports) in the store: an Asus
P4P800.
My
On Friday, 26 September 2003 at 22:08:25 -0400, David Gilbert wrote:
>>>>>> "Greg" == Greg Lehey writes:
>
> Greg> Don't hold your breath. This will probably happen in the course
> Greg> of migrating Vinum functionality to GEOM.
>
> So... i
>>>>> "Greg" == Greg Lehey writes:
Greg> Don't hold your breath. This will probably happen in the course
Greg> of migrating Vinum functionality to GEOM.
So... is vinum-as-we-know-it going to disappear into the GEOM monster?
There se
On Friday, 26 September 2003 at 19:28:45 -0400, David Gilbert wrote:
>>>>>> "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:
>
> Robert> On Fri, 26 Sep 2003, David Gilbert wrote:
>
>>> Recent changes to -CURRENT prohibit vinum swap:
>
>>>>> "Robert" == Robert Watson <[EMAIL PROTECTED]> writes:
Robert> On Fri, 26 Sep 2003, David Gilbert wrote:
>> Recent changes to -CURRENT prohibit vinum swap:
>>
>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon:
>> /de
On Sat, 27 Sep 2003, Greg 'groggy' Lehey wrote:
> > I recently noticed that Vinum may be averse to blocksizes other than
> > 512 bytes.
>
> It shouldn't be. There's never been any dependency on it.
I've attached the output from trying to use a swap
On Friday, 26 September 2003 at 18:38:48 -0400, Robert Watson wrote:
>
> On Fri, 26 Sep 2003, David Gilbert wrote:
>
>> Recent changes to -CURRENT prohibit vinum swap:
>>
>> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon: /dev/vinum/swapmu:
>> Oper
On Fri, 26 Sep 2003, David Gilbert wrote:
> Recent changes to -CURRENT prohibit vinum swap:
>
> [1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu swapon: /dev/vinum/swapmu:
> Operation not supported by device
In order to support swapping, Vinum will need to be modified to use
Recent changes to -CURRENT prohibit vinum swap:
[1:6:[EMAIL PROTECTED]:~> swapon /dev/vinum/swapmu
swapon: /dev/vinum/swapmu: Operation not supported by device
Dave.
--
|David Gilbert, Independent Contrac
Some changes in device driver locking recently broke Vinum for a short
period of time. The problem is now fixed. If you have any problems
with a recent version of Vinum, please let me know.
Greg
--
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
msgbuf cksum mismatch (read a5886, calc
Greg 'groggy' Lehey wrote:
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disk
In message: <[EMAIL PROTECTED]>
Wilko Bulte <[EMAIL PROTECTED]> writes:
: On Sat, Aug 09, 2003 at 06:38:51AM +0200, Poul-Henning Kamp wrote:
: > In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
: > writes:
: >
: > >> and
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
> Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Rob writes:
>>
>>> Hi all,
>>>
>>> After cvs'upping (about 12 hours ago) and building world/kernel vinum
>>> stopp
Its wierd though that it works on intel/p4 but gets taht panic: Giant on
amd... My 2 amd systems panic with vinum start but the P4 works ok built
from the same sources. All with no vinum volumes, just trying vinum
start t test for this bug.
- Original message -
From: "Poul-Henning
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try
[Format recovered--see http://www.lemis.com/email/email-format.html]
Long/short syndrome.
On Tuesday, 12 August 2003 at 20:49:05 -0400, James Quick wrote:
>
> I am seeking feedback on the status of vinum, and whether the
> following plan makes sense as an upgrade plan for a host with
In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
> Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198
Ok, then I think I know what it is.
Vinum appearantly does not go through SPECFS but rather calls into
the disk device drivers directly. That is a prett
In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>I just cvsuped -current this afternoon to get about 1 weeks updates.
>After that the kernel panics booting starting vinum. I removed the one
>vinum volume (reformated as UFS2) I had for testing. And it still pan
used for data. Each pair of production and test
slices will be periodically mirrored to it's twin to provide a measure
of fault tolerance. The box currently has one of the two new large
drives
installed, and 3 smaller aging (and ailing) drives.
I was hoping to use vinum for all the rest,
I just cvsuped -current this afternoon to get about 1 weeks updates.
After that the kernel panics booting starting vinum. I removed the one
vinum volume (reformated as UFS2) I had for testing. And it still panics.
I changed the /etc/rc.conf
start_vinum="YES" to NO and can st
On Fri, Aug 08, 2003 at 10:22:06AM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
> >I just cvsuped -current this afternoon to get about 1 weeks updates.
> >After that the kernel panics booting starting vinum. I removed the
On Thursday, 7 August 2003 at 18:23:10 -0600, Aaron Wohl wrote:
> I just cvsuped -current this afternoon to get about 1 weeks updates.
> After that the kernel panics booting starting vinum. I removed the one
> vinum volume (reformated as UFS2) I had for testing. And it still panics.
>
On Sat, Aug 09, 2003 at 06:38:51AM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
> writes:
>
> >> and it seems that vinum does not respect the D_NOGIANT flag which
> >> GEOM recently started setting.
On Friday, 8 August 2003 at 15:24:09 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>
>> Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198
>
> Ok, then I think I know what it is.
>
> Vinum appearant
gt;>> Hi all,
>>>>>
>>>>> After cvs'upping (about 12 hours ago) and building world/kernel vinum
>>>>> stopped working. It does show my two disks but nothing more. I also
>>>>> get an error message right after the bootloader:
&g
I tried it this morning on different systems. So far the two AMD systems
panic with vinum start and the intel/p4 works ok. All systems have no
vinum volumes currently.
Good dump found on device /dev/ad0s1b
Architecture: i386
Architecture version: 1
Dump length: 1073676288B (1023 MB
In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
writes:
>> and it seems that vinum does not respect the D_NOGIANT flag which
>> GEOM recently started setting.
>
>Probably because it didn't know about it. As I've said before, it
>wou
.
>>> After that the kernel panics booting starting vinum. I removed the one
>>> vinum volume (reformated as UFS2) I had for testing. And it still panics.
>>> I changed the /etc/rc.conf
>>> start_vinum="YES" to NO and can start ok now.
>>
>>
In message <[EMAIL PROTECTED]>, Rob writes:
>Hi all,
>
>After cvs'upping (about 12 hours ago) and building world/kernel vinum
>stopped working. It does show my two disks but nothing more. I also
>get an error message right after the bootloader:
Can you try this pa
--On 2. august 2003 11:16 +0200 Bernd Walter <[EMAIL PROTECTED]>
wrote:
Looks like a problem in vinum. The other backtrace was the same, right?
Please take a look at an older thread named (IIRC) vinum or geom bug?
Greg asked for special debug output, but it never happened again for me.
fff,47) at
launch_requests+0x448 vinumstart(c5ada2d0,0,c22ab000,cfb5294c,c02e5bc6)
at vinumstart+0x2b2 vinumstrategy(c5ada2d0,0,c09719b0,40,0) at
vinumstrategy+0xa6
Looks like a problem in vinum. The other backtrace was the same, right?
Basically the same, yes. Some differences (and many similarities) in
,47) at launch_requests+0x448
> > vinumstart(c5ada2d0,0,c22ab000,cfb5294c,c02e5bc6) at vinumstart+0x2b2
> > vinumstrategy(c5ada2d0,0,c09719b0,40,0) at vinumstrategy+0xa6
>
> Looks like a problem in vinum. The other backtrace was the same, right?
Please take a look at an olde
inumstart+0x2b2
> vinumstrategy(c5ada2d0,0,c09719b0,40,0) at vinumstrategy+0xa6
Looks like a problem in vinum. The other backtrace was the same, right?
Kris
pgp0.pgp
Description: PGP signature
Hi All,
I'm just trying to learn vinum so am trying to create a stripe out of 2 MD
disk disks.
I've create two md deivce //dev/md[01]
then
fieldpoint# bsdlabel -w /dev/md0
fieldpoint# bsdlabel -w /dev/md1
fieldpoint# vinum
vinum -> stripe /dev/md0h /dev/md1h
Can't create
On Wednesday, 9 July 2003 at 21:40:43 +0100, Chris Hedley wrote:
> Hi all,
>
> I had a quick look for the subject topic but didn't find anything, so...
> is anybody aware of outstanding problems with vinum? I'm getting sporadic
> crashes (see below) and vinum frequentl
Hi all,
I had a quick look for the subject topic but didn't find anything, so...
is anybody aware of outstanding problems with vinum? I'm getting sporadic
crashes (see below) and vinum frequently fails to start properly, losing
state information and occasionally barfing when an attem
David Gilbert wrote:
So the release notes say that you can boot from a vinum partition.
They don't give any details (raid 5 support, etc) and neither does any
of the documentation that I've managed to track down.
So ... I'm using a hard disk to boot while I put vinum on all th
So the release notes say that you can boot from a vinum partition.
They don't give any details (raid 5 support, etc) and neither does any
of the documentation that I've managed to track down.
So ... I'm using a hard disk to boot while I put vinum on all the
drives in the server
On Sat, Jun 14, 2003 at 03:15:27PM +0930, Greg 'groggy' Lehey wrote:
> On Tuesday, 10 June 2003 at 14:05:11 +0200, Bernd Walter wrote:
> >
> > fatal kernel trap:
> >
> > Stopped at g_dev_strategy+0x44:stq t0,0x20(v0) <0x20>
> >
> > db> trace
> > g_dev_strategy() at g_dev_strateg
On Tuesday, 10 June 2003 at 14:05:11 +0200, Bernd Walter wrote:
>
> fatal kernel trap:
>
> Stopped at g_dev_strategy+0x44:stq t0,0x20(v0) <0x20>
>
> db> trace
> g_dev_strategy() at g_dev_strategy+0x44
> launch_requests() at launch_requests+0x390
> prologue botch: displacement 12
cause = load instructon
pc = 0xfc559c00
ra = 0xfc55a250
sp = 0xfe000b7bb428
curthread = 0xfc000f726940
pid = 8, comm = syncer
Stopped at decode_prologue+0x60: ldl s0,0(s1) <0x41>
Vinum
On Tue, 25 Mar 2003, Kenneth D. Merry wrote:
KDM>On Wed, Mar 26, 2003 at 11:06:52 +1030, Greg 'groggy' Lehey wrote:
KDM>> On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote:
KDM>> >
KDM>> > Hi,
KDM>> >
KDM>> > when calling &#x
On Wed, Mar 26, 2003 at 11:06:52 +1030, Greg 'groggy' Lehey wrote:
> On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote:
> >
> > Hi,
> >
> > when calling 'vinum start' it responds with
> >
> > usage: read drive [drive ...]
On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote:
>
> Hi,
>
> when calling 'vinum start' it responds with
>
> usage: read drive [drive ...]
>
> from looking at the code, it appears that it cannot find the disk drives
> to read the confi
Hi,
when calling 'vinum start' it responds with
usage: read drive [drive ...]
from looking at the code, it appears that it cannot find the disk drives
to read the configuration from.
vinum read da0 da1
just works.
So what's the problem? (kernel and user land from today)
On Sun, Mar 16, 2003 at 09:20:10AM +1030, Greg 'groggy' Lehey
<[EMAIL PROTECTED]> wrote:
> >>> Will it suffice to switch off power for one disk to simulate "more"
> >>> real-world disk failure? Are there any hidden pitfalls for failing
> >>> and restoring operation of non-hotswap disks?
> >>
> >>
On Saturday, 15 March 2003 at 23:56:24 +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
> writes:
>
>>> Ok, I'll try to simulate the disk failure by switching off the
>>> power, then.
>>
>> I think you misunderstand. I simulated the disk failures by doing a
In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
writes:
>> Ok, I'll try to simulate the disk failure by switching off the
>> power, then.
>
>I think you misunderstand. I simulated the disk failures by doing a
>"stop -f". I can't see any way that the way they go down can
>influence the rev
ctl -iv raid?). So I used the
>>> raidframe patch for -stable at
>>> http://people.freebsd.org/~scottl/rf/2001-08-28-RAIDframe-stable.diff.gz
>>> Had to do some patching by hand, but otherwise works well.
>>
>> I don't think that problems with RAIDFrame are r
people.freebsd.org/~scottl/rf/2001-08-28-RAIDframe-stable.diff.gz
> > Had to do some patching by hand, but otherwise works well.
>
> I don't think that problems with RAIDFrame are related to these
> problems with Vinum. I seem to remember a commit to the head branch
> recen
t, I'm very sorry to say it.
>>
>> Sorry for the slow reply to this. I thought it would make sense to
>> try things out here, and so I kept trying to find time, but I have to
>> admit I just don't have it yet for a while. I haven't forgotten, and
>> I ho
ught it would make sense to
> try things out here, and so I kept trying to find time, but I have to
> admit I just don't have it yet for a while. I haven't forgotten, and
> I hope that in a few weeks time I can spend some time chasing down a
> whole lot of Vinum issues. This is
On Saturday, 1 March 2003 at 20:43:10 +0200, Vallo Kallaste wrote:
> On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste wrote:
>
>>>> The vinum R5 and system as a whole were stable without
>>>> softupdates. Only one problem remained after disabling softupdate
On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste wrote:
> > > The vinum R5 and system as a whole were stable without
> > > softupdates. Only one problem remained after disabling softupdates,
> > > while being online and user I/O going on, rebuilding of faile
On Thu, Feb 27, 2003 at 11:59:59AM +1030, Greg 'groggy' Lehey
<[EMAIL PROTECTED]> wrote:
> > The crashes and anomalies with filesystem residing on R5 volume were
> > related to vinum(R5)/softupdates combo.
>
> Well, at one point we suspected that. But the c
On Friday, 21 February 2003 at 1:56:56 -0800, Terry Lambert wrote:
> Vallo Kallaste wrote:
>> The crashes and anomalies with filesystem residing on R5 volume were
>> related to vinum(R5)/softupdates combo. The vinum R5 and system as
>> a whole were stable without softupda
On Friday, 21 February 2003 at 10:00:46 +0200, Vallo Kallaste wrote:
> On Thu, Feb 20, 2003 at 02:28:45PM -0800, Darryl Okahata
> <[EMAIL PROTECTED]> wrote:
>
>> Vallo Kallaste <[EMAIL PROTECTED]> wrote:
>>
>>> I'll second Brad's statement a
Darryl Okahata wrote:
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> > I think this is an expected problem with a lot of concatenation,
> > whether through Vinum, GEOM, RAIDFrame, or whatever.
> >
> > This comes about for the same reason that you can't "m
Terry Lambert <[EMAIL PROTECTED]> wrote:
> I think this is an expected problem with a lot of concatenation,
> whether through Vinum, GEOM, RAIDFrame, or whatever.
>
> This comes about for the same reason that you can't "mount -u"
> to turn Soft Updates from
Vallo Kallaste wrote:
> The crashes and anomalies with filesystem residing on R5 volume were
> related to vinum(R5)/softupdates combo. The vinum R5 and system as
> a whole were stable without softupdates. Only one problem remained
> after disabling softupdates, while being online
On Thu, Feb 20, 2003 at 02:28:45PM -0800, Darryl Okahata
<[EMAIL PROTECTED]> wrote:
> Vallo Kallaste <[EMAIL PROTECTED]> wrote:
>
> > I'll second Brad's statement about vinum and softupdates
> > interactions. My last experiments with vinum were more than h
ur /boot/loader.conf, /and/ remove the start_vinum line from
>>> rc.conf. Please tell me whether this gives different results.
>
> Bad things happen when doing the above.
> Vinum forgets his configuration on loading.
>
> I did the following:
> 1.) Configure a volume as:
&
On Saturday, 8 February 2003 at 21:42:27 +0100, Joerg Wunsch wrote:
> As Greg 'groggy' Lehey wrote:
>
>>> I guess it's time to dump the old vinum start code from
>>> vinum(8) completely, and use the in-kernel scan now.
>>
>> This sounds l
As Greg 'groggy' Lehey wrote:
> > I guess it's time to dump the old vinum start code from
> > vinum(8) completely, and use the in-kernel scan now.
>
> This sounds like a good idea.
Not after looking a bit closer. ;-) The only difference ist that the
userland
this gives different results.
Bad things happen when doing the above.
Vinum forgets his configuration on loading.
I did the following:
1.) Configure a volume as:
drive d0 device /dev/da0s1a
drive d1 device /dev/da1s1a
volume ablage setupstate
plex name ablage.p0 org concat
sd name ablage.p0.s0
On Saturday, 8 February 2003 at 0:00:45 +0100, Joerg Wunsch wrote:
> As Michael Reifenberger wrote:
>
>>> What does your sysctl kern.disks say?
>>
>> (nihil)(root) # sysctl -a kern.disks
>> kern.disks: da1 da0 ad1 ad0
>
> That's OK.
>
> I gue
As Michael Reifenberger wrote:
> > What does your sysctl kern.disks say?
>
> (nihil)(root) # sysctl -a kern.disks
> kern.disks: da1 da0 ad1 ad0
That's OK.
I guess it's time to dump the old vinum start code from
vinum(8) completely, and use the in-kernel sc
1 - 100 of 645 matches
Mail list logo
