Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Apr 1998 16:11:22 -0500
From:      Raul Zighelboim <rzig@verio.net>
To:        "'Kenneth D. Merry'" <ken@plutotech.com>
Cc:        scsi@FreeBSD.ORG
Subject:   RE: Help ! Scsi buss going down !
Message-ID:  <A03CD00C69B1D01195AB00A024ECEB167F9DDA@kaori.communique.net>

next in thread | raw e-mail | index | archive | help

were leaving the adaptec and getting a dpt for this server soon (as fast
as UPS can deliver), so, no, not considered CAM at this point.

In any case, it seems that we track down the problem (the initial
problem, not the one we caused trying to fix it ;-|)
We had an adaptec card going bad, we got a replacement (revision E of
the bios) that was worse than bad.


==================================================
Raul Zighelboim       		  rzig@verio.net

> -----Original Message-----
> From:	Kenneth D. Merry [SMTP:ken@plutotech.com]
> Sent:	Monday, April 20, 1998 11:32 AM
> To:	Raul Zighelboim
> Cc:	scsi@FreeBSD.ORG
> Subject:	Re: Help ! Scsi buss going down !
> 
> Raul Zighelboim wrote...
> > 
> > This system seems to have suffer from a massive stroke!
> > 
> > With lots of testing, we got to the same conclusion yesterday
> revision E
> > has problems over load (run iozone and see the system freeze).  I am
> > running 3 revision D cards, but maybe one of them is defective.  We
> will
> > keep replacing cards.
> 
> 	Have you considered running CAM?  There are many bugs that have
> been fixed in the CAM version of the Adaptec driver.  At the very
> least,
> the error recovery code in CAM is generally better than the old code,
> so
> that might help stabilize your system somewhat.  To see what is
> involved,
> see:
> 
> ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README
> 
> or
> 
> ftp://ftp.kdm.org/pub/FreeBSD/cam/README
> 
> 	You'll have to run -current, which may or may not work in your
> case.  If not, you'll have to wait until Justin gets time to port CAM
> to
> 2.2-stable.
> 
> > Unrelated , every time we reboot the server, we get an error message
> at
> > reboot.  It does not matter how clean the shutdown was: (sync; sync;
> > sync; /sbin/umount -a; /sbin/shutdown -h now)...
> > 
> > fsck complains at reboot:
> > Cannot alloc 3317710 bytes for blockmap
> > Cannot check file system
> > ....
> > running fsck manually will show a clean fs.
> > 
> > Any idea on how I can fix this >?
> 
> 	You need to adjust the amount of memory that the 'daemon' class
> is
> allowed to use in /etc/login.conf.  Problems like that typically show
> up
> when you try to fsck a large filesystem, or run savecore on a RAM
> image
> from a system with a lot of memory.
> 
> Ken
> --
> Kenneth Merry
> ken@plutotech.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A03CD00C69B1D01195AB00A024ECEB167F9DDA>