From owner-freebsd-fs@FreeBSD.ORG  Thu Apr 11 20:47:52 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 7146BDFB
 for <freebsd-fs@freebsd.org>; Thu, 11 Apr 2013 20:47:52 +0000 (UTC)
 (envelope-from radiomlodychbandytow@o2.pl)
Received: from moh2-ve2.go2.pl (moh2-ve2.go2.pl [193.17.41.200])
 by mx1.freebsd.org (Postfix) with ESMTP id 33ACA1A64
 for <freebsd-fs@freebsd.org>; Thu, 11 Apr 2013 20:47:51 +0000 (UTC)
Received: from moh2-ve2.go2.pl (unknown [10.0.0.200])
 by moh2-ve2.go2.pl (Postfix) with ESMTP id 79367B0156B
 for <freebsd-fs@freebsd.org>; Thu, 11 Apr 2013 22:47:44 +0200 (CEST)
Received: from unknown (unknown [10.0.0.108])
 by moh2-ve2.go2.pl (Postfix) with SMTP
 for <freebsd-fs@freebsd.org>; Thu, 11 Apr 2013 22:47:43 +0200 (CEST)
Received: from unknown [93.175.66.185] by poczta.o2.pl with ESMTP id rQjzzC;
 Thu, 11 Apr 2013 22:47:43 +0200
Message-ID: <51672164.1090908@o2.pl>
Date: Thu, 11 Apr 2013 22:47:32 +0200
From: =?UTF-8?B?UmFkaW8gbcWCb2R5Y2ggYmFuZHl0w7N3?= <radiomlodychbandytow@o2.pl>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130324 Thunderbird/17.0.4
MIME-Version: 1.0
CC: freebsd-fs@freebsd.org
Subject: A failed drive causes system to hang
References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org>
In-Reply-To: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-O2-Trust: 1, 37
X-O2-SPF: neutral
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2013 20:47:52 -0000

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...
-- 
Twoje radio