Date: Fri, 08 Dec 2000 02:43:28 -0800 From: Mike Smith <msmith@freebsd.org> To: Mark Newton <newton@internode.com.au> Cc: Tomi Vainio - Sun Finland - <Tomi.Vainio@Sun.COM>, freebsd-current@FreeBSD.ORG Subject: Re: ffs_valloc: dup alloc panics with stable/current Message-ID: <200012081043.eB8AhSF09030@mass.osd.bsdi.com> In-Reply-To: Your message of "Fri, 08 Dec 2000 12:19:09 %2B1030." <20001208121909.D80963@internode.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, Dec 08, 2000 at 03:44:28AM +0200, Tomi Vainio - Sun Finland - wrote:
>
> > sense = 3 asc = 11 asq = 0
> > This is not so bad but 5-30 minutes after this command system will
> > always panic.
>
> Are you surprised? The system is complaining that it's having intermittent
> difficulty accessing the disk, so it shouldn't be at all surprising that
> you'd have disk corruption problems as a result.
Actually, it's upstream from the RAID controller. There don't appear to
be any actual complaints from the controller about read errors, so I'm a
little skeptical that this is actually the "real" problem.
> Start by checking your SCSI cabling and termination. Almost all SCSI
> problems boil down to that eventually.
The entire system; disks, controller, etc. is all pretty skanky by the
sound of it. It wouldn't surprise me too much if the system is suffering
eg. multiple-master data corruption, or straight out memory/cache errors.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012081043.eB8AhSF09030>