From owner-freebsd-fs@FreeBSD.ORG Thu Apr 11 21:03:06 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5103AFFC for ; Thu, 11 Apr 2013 21:03:06 +0000 (UTC) (envelope-from prvs=1813db02ab=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id EB0441B35 for ; Thu, 11 Apr 2013 21:03:04 +0000 (UTC) Received: from r2d2 ([46.65.172.4]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50003224210.msg for ; Thu, 11 Apr 2013 22:02:55 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 11 Apr 2013 22:02:55 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 46.65.172.4 X-Return-Path: prvs=1813db02ab=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <41A207817BC94167B0C94133EC0DFD68@multiplay.co.uk> From: "Steven Hartland" To: =?iso-8859-1?Q?Radio_mlodych_bandyt=F3w?= References: <51672164.1090908@o2.pl> Subject: Re: A failed drive causes system to hang Date: Thu, 11 Apr 2013 22:03:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2013 21:03:06 -0000 ----- Original Message ----- From: "Radio mlodych bandytów" > Seeing a ZFS thread, I decided to write about a similar problem that I experience. > I have a failing drive in my array. I need to RMA it, but don't have time and it fails rarely enough to be a yet another > annoyance. > The failure is simple: it fails to respond. > When it happens, the only thing I found I can do is switch consoles. Any command fails, login fails, apps hang. > > On the 1st console I see a series of messages like: > > (ada0:ahcich0:0:0:0): CAM status: Command timeout > (ada0:ahcich0:0:0:0): Error 5, Periph was invalidated > (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED > > I use RAIDZ1 and I'd expect that none single failure would cause the system to fail... OS version? ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.