From owner-freebsd-current Thu Dec 7 17:50:30 2000 From owner-freebsd-current@FreeBSD.ORG Thu Dec 7 17:50:28 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id EC5E437B401 for ; Thu, 7 Dec 2000 17:50:25 -0800 (PST) Received: (from newton@localhost) by gizmo.internode.com.au (8.11.0/8.9.3) id eB81n9V81115; Fri, 8 Dec 2000 12:19:09 +1030 (CST) (envelope-from newton) Date: Fri, 8 Dec 2000 12:19:09 +1030 From: Mark Newton To: Tomi Vainio - Sun Finland - Cc: freebsd-current@FreeBSD.ORG Subject: Re: ffs_valloc: dup alloc panics with stable/current Message-ID: <20001208121909.D80963@internode.com.au> References: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <14896.15612.659070.165662@ultrahot.Finland.Sun.COM> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: newton@gizmo.internode.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Start by checking your SCSI cabling and termination. Almost all SCSI problems boil down to that eventually. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message