From owner-freebsd-fs@FreeBSD.ORG Thu Mar 15 09:51:39 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E20B1065674 for ; Thu, 15 Mar 2012 09:51:39 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 56E708FC14 for ; Thu, 15 Mar 2012 09:51:38 +0000 (UTC) Received: by vcmm1 with SMTP id m1so4024051vcm.13 for ; Thu, 15 Mar 2012 02:51:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=DdgX6kbFCrdmBatY9kkkT3TCfspWl9kJ7U4kYrH7+lA=; b=t58R1395qDg1XKhXTClXJtaH8oHYXBb/pi0ArbJ/7OZtw1+t9CyaI85h6K26Jbrm9u O2nmi/lb4DFAkaImXfMlFj+17AtwpcquqvS4gDB5SS9Y0Jp4lrcoimuQb7WwI1s+Mjir HnK8JYZv61W+7nlMaLhtYv+Nc5Z/YVx31vcu3asDgUflfsIHWlckVygpi1pDBp2UV7pA yUGgNpRbKTRoJCZOvX8kOs0lQtJFQmKYdYEcPDzp9jgatT808x1i4PTsA73ifkdJRPeW FITnmaevBc5KAwUnjeenKdBwIx4iLUTYu4R7bul4Gyxixtt9J7rKCMSllHQKllvAlkL7 VQZw== MIME-Version: 1.0 Received: by 10.52.72.74 with SMTP id b10mr4348060vdv.85.1331805098374; Thu, 15 Mar 2012 02:51:38 -0700 (PDT) Received: by 10.220.38.67 with HTTP; Thu, 15 Mar 2012 02:51:38 -0700 (PDT) In-Reply-To: <4F60D73F.2010201@intellasoft.net> References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de> <4F60266D.1090302@intellasoft.net> <4F60D73F.2010201@intellasoft.net> Date: Thu, 15 Mar 2012 11:51:38 +0200 Message-ID: From: George Kontostanos To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: ZFS file corruption problem X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 09:51:39 -0000 On Wed, Mar 14, 2012 at 7:37 PM, Mark Murawski wrote: > On 03/14/12 10:03, Bob Friesenhahn wrote: >> >> On Wed, 14 Mar 2012, Mark Murawski wrote: >>> >>> >>> Why would the whole pool now become available upon access to a bad file= ? >> >> >> A disk drive (or HBA) may be hanging (e.g. endless retries) when the bad >> file is accessed. This is a common problem with consumer disks or HBAs >> which believe they are the top level authority when it comes to data >> integrity. Zfs itself does not include any timers to decide to stop >> waiting. Zfs depends on the lower-level OS & drivers to decide to stop >> waiting on a stalled device. >> >> Bob > > > > Ah okay. =A0And you assumed correctly that I had meant "become unavailabl= e > upon access". > > This is probably related to the bug I'm experiencing on my Promise SATA 3= 00 > TX4 controller > (http://lists.freebsd.org/pipermail/freebsd-bugs/2012-March/047998.html) > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" Yes, as a matter of fact: http://www.aisecure.net/2011/07/07/promise-pdc40718-sata300-junk/ --=20 George Kontostanos Aicom telecoms ltd http://www.aisecure.net