Hi
In the last ~three months now I've had 24 kernel crashes, all the
same, all happening in the same circumstances. Happens while cvsup
is running, everytime... except if I remove the checkouts file which
probably causes slowdown of cvsup operation. I have recreated the
filesystem on /dev/da2s1e s
Hi,
Looks like bad hw. Have you run memtestx86 on this machine
about 2-3 hours ? I had the same effects on one machine ...
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse
On Wed, Feb 05, 2003 at 11:47:44AM +0200, Vallo Kallaste wrote:
> ---
> panic: ufs_dirbad: bad dir
> cpuid = 1; lapic.id = 0100
> boot() called on cpu#1
I get those on the bento cluster when the disk is starting to fail.
dd'ing /dev/zero over it usually gives it some more life by forcing it
t
On Wed, Feb 05, 2003 at 10:40:09AM -0800, Kris Kennaway
<[EMAIL PROTECTED]> wrote:
> > ---
> > panic: ufs_dirbad: bad dir
> > cpuid = 1; lapic.id = 0100
> > boot() called on cpu#1
>
> I get those on the bento cluster when the disk is starting to fail.
> dd'ing /dev/zero over it usually gives
On Wed, Feb 05, 2003 at 11:47:44AM +0200, Vallo Kallaste wrote:
> accumulated filesystem corruption. This is on UFS2 filesystem,
> haven't tried UFS1 yet. World and kernel are from January 21, PIII
> SMP system. I'll provide any info one needs to track the cause,
> needless to say I'm _really_ ti
On Wed, Feb 05, 2003 at 11:47:44AM +0200, Vallo Kallaste wrote:
> In the last ~three months now I've had 24 kernel crashes, all the
> same, all happening in the same circumstances. Happens while cvsup
> is running, everytime... except if I remove the checkouts file which
> probably causes slowdow
