Re: SCSI device timeouts.

In message <[EMAIL PROTECTED]>, "f.joha n.beisser" writes: > > i've been having a problem as of late, that's not really gone away. > > from the console log: > (da0:ahc0:0:0:0): SCB 0x3 - timed out while idle, SEQADDR == 0x4 > STACK == 0x1, 0x174, 0x15e, 0x0 > > i get one of these errors, and

Re: 4.2-STABLE build fails

>> Original Message << On 1/5/01, 4:18:43 PM, Keith Jones <[EMAIL PROTECTED]> wrote regarding Re: 4.2-STABLE build fails: > On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > > I've seen much of this discussed here but mine seems to break

Re: Problems with corrupted vinum devices...

At 5:44 PM +0100 2001/1/5, [EMAIL PROTECTED] wrote: > diff -ru /tmp/vinum/vinumvar.h ./vinumvar.h > --- /tmp/vinum/vinumvar.hMon May 22 18:21:37 2000 > +++ ./vinumvar.h Thu Jan 4 19:12:01 2001 > @@ -158,15 +158,15 @@ >* probably too small. >*/ > > -INITIAL_DRIVES = 4, >

Re: Problems with corrupted vinum devices...

At 5:44 PM +0100 2001/1/5, [EMAIL PROTECTED] wrote: > I suggest increasing INITIAL_DRIVES in vinumvar.h to avoid array > resize and the associated race conditions. When I tried to configure > vinum to use 14 disks yesterday, the machine immediately crashed with > a trap 12 in response to 'vi

SCSI device timeouts.

i've been having a problem as of late, that's not really gone away. from the console log: (da0:ahc0:0:0:0): SCB 0x3 - timed out while idle, SEQADDR == 0x4 STACK == 0x1, 0x174, 0x15e, 0x0 i get one of these errors, and after that, the disk does not recover at all. in this case, it's my main dis

Re: Problems with corrupted vinum devices...

> However, at some point within the next couple of hours (we're not > quite sure when), the machine crashed, and vinum failed to come up on > the reboot. We had to comment out the /etc/fstab entries that > referred to the vinum volumes, and since then have been trying to > debug the pro

Re: 4.2-STABLE build fails

* Janko van Roosmalen <[EMAIL PROTECTED]> [20010105 17:06]: writing on the subject 'Re: 4.2-STABLE build fails' Janko> On Thu, 4 Jan 2001, Odhiambo Washington wrote: Janko> Janko> > Hi Janko> > I've seen much of this discussed here but mine seems to break

Problems with corrupted vinum devices...

Folks, I've read the man page, the vinum debugging page at , searched the archives of the stable mailing list, and still haven't found anything that would appear to address the situation we've just started experiencing. Many mo

Re: termcap

On Fri, Jan 05, 2001 at 10:02:31AM +0100, Michel Talon wrote: > On Fri, Jan 05, 2001 at 12:20:49AM -0600, Victor R. Cardona wrote: > > Hi everyone, > > > > I have been experiencing problems on 4.x-STABLE for the last couple of > > days. /etc/termcap exists, and it points to a real termcap file. H

Re: 4.2-STABLE build fails

On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > I've seen much of this discussed here but mine seems to break at this > > point: > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > ..and with this msg on the console... > > > > Jan 3 18:54:07 alouette /k

Re: Vinum Question

Hi, dxoch wrote on Fri, Jan 05, 2001 at 03:21:55PM +: [..] > vi /boot/defaults/loader.conf and you will find: vinum_load="NO" True I missed that... [..] > > Although I guess you could immediately load the vinum.ko, > > before booting the kernel (i.e. load the kernel, load the > > module alo

Re: Vinum Question

Daniel Lang wrote: > Hi Jim, > > [..] > > Is there is any chance that vinum-related options in the loader.conf > > (vinum_load ="YES") > > can help me to boot from a vimum volume, or this is completely > > irrelevant? > > I guess so. I know of 'vinum_load="YES"' only in /etc/rc.conf, > not load

Re: 4.2-STABLE build fails

On Thu, 4 Jan 2001, Odhiambo Washington wrote: > Hi > I've seen much of this discussed here but mine seems to break at this > point: > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > ..and with this msg on the console... > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: