From owner-freebsd-stable@FreeBSD.ORG Fri Jun 20 14:44:56 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 054BF37B401 for ; Fri, 20 Jun 2003 14:44:56 -0700 (PDT) Received: from mail.hitmedia.com (mail.hitmedia.com [205.162.11.163]) by mx1.FreeBSD.org (Postfix) with SMTP id 2AB5D43FE1 for ; Fri, 20 Jun 2003 14:44:44 -0700 (PDT) (envelope-from ryanlists@hostbaby.com) Received: (qmail 43535 invoked from network); 20 Jun 2003 21:44:46 -0000 Received: from unknown (HELO localhost.columbia80.com.) (127.0.0.1) by localhost with SMTP; 20 Jun 2003 21:44:46 -0000 From: Ryan O'Neill To: "Scott R. Sewall" , stable@freebsd.org Date: Fri, 20 Jun 2003 14:44:46 -0700 User-Agent: KMail/1.5.2 References: <3EF2A452.156DF49E@ix.netcom.com> In-Reply-To: <3EF2A452.156DF49E@ix.netcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200306201444.46417.ryanlists@hostbaby.com> Subject: Re: pst: timeout mfa=0x00327b90 cmd=WRITE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jun 2003 21:44:56 -0000 On Thursday 19 June 2003 11:06 pm, Scott R. Sewall wrote: > I installed a Promise SuperTrak SX6000 ATA RAID controller on 4.8-RELEASE. > > The following message is logged when the device is under load (equivalent > of make release): pst: timeout mfa=0x00327b90 cmd=WRITE > > Should I be concerned? We haven't been :) We're using that same card and we've been getting those messages for both WRITE and READ occassionally ever since our came up 4 and a half months ago. We haven't noticed any problems relating to those errors in particular. Stuff seems to still work fine. bash-2.05b# gunzip /var/log/messages*.gz && \ > cat /var/log/messages* | grep "pst: timeout" | wc -l 529 The only thing that bugs me is the fact that the box takes about half an hour to reboot, even when the raid has been cleanly dismounted (don't even ask how long it takes when it needs to be fsk'ed). If you (or anyone) finds or has a better answer for the timeout error or the reboot thing, please do share :) -- HOSTBABY.COM - web hosting for musicians Ryan O'Neill - ryan@hostbaby.com http://www.hostbaby.com