From owner-freebsd-geom@FreeBSD.ORG Fri May 11 11:32:23 2012 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1C28106566B for ; Fri, 11 May 2012 11:32:23 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 56E018FC14 for ; Fri, 11 May 2012 11:32:23 +0000 (UTC) Received: by yenl8 with SMTP id l8so3240512yen.13 for ; Fri, 11 May 2012 04:32:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=yuzjt/VIsDfFhXCFv/kX+qAFUpJagl5iBvZ3ixqUq3U=; b=B4EEaD/vwluy/r6pu1rqRjyzj0VrjXHzkhnC+Ut3t/Aso1mP6hC5uB7YE95sFXMZ5S T+gZlBymkajU0rTdz8P/LlQxU4IwSHLCqs/ARCQZDFoLH4NtYN0c28Nf949xU/UiGoFN fKF7KKSgBfKe1lSd3XKGkQBLKms3vGHKPNiDtmcmYCmCUDRKCLDTdvnnQIL8RHYHGZ9k hmSH0g6V2axlcj5wqlIyMTitPZWja8AdSmvafPJOVZP7phvcyWXj6Ex3oPQUVepjJlLL LNLtiPTE2JqjWjwiyxC/Vyc2HKvCwjqAMpCIcqnwAQmejR7Ac/X3AzbXh8hE51rStNYo u77g== Received: by 10.50.169.3 with SMTP id aa3mr1452673igc.28.1336735942502; Fri, 11 May 2012 04:32:22 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([24.114.252.240]) by mx.google.com with ESMTPS id wh8sm5501325igb.11.2012.05.11.04.32.21 (version=SSLv3 cipher=OTHER); Fri, 11 May 2012 04:32:21 -0700 (PDT) Sender: Alexander Motin Message-ID: <4FACF8BA.4020500@FreeBSD.org> Date: Fri, 11 May 2012 14:32:10 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120116 Thunderbird/9.0 MIME-Version: 1.0 To: Karl Pielorz References: <4FABDE10.8090304@FreeBSD.org> <61CDA17B687F1C733EE1B017@OctaHexa64-MkII> In-Reply-To: <61CDA17B687F1C733EE1B017@OctaHexa64-MkII> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-geom@FreeBSD.org Subject: Re: FreeBSD 9-R amd64 - graid, should it survive 'pulling' a disk? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2012 11:32:23 -0000 On 11.05.2012 14:08, Karl Pielorz wrote: > --On 10 May 2012 18:26 +0300 Alexander Motin wrote: >> This panic is not in graid code, but it can be called a problem of the >> graid's RAID1 implementation. If some disk returns _write_ failure, that >> failure may now be reported to higher levels. Problem is that UFS SU code >> panics on these errors in some cases. I'll try to look on it nearest >> time. > > So for clarity - what you're saying is if one of the servers drops a > disk from it's graid RAID1 array (for whatever reason) while writing, > the error could 'bubble up' and have the UFS code panic, because of it? > (even though the write would have completed on the other drive)? Yes, sometimes bubble and in rare cases panic. I am working on the first part right now. > Is the same true for reads? No, On read error graid repeats reading from another disk and does remapping write to the original one. Error returned only if all reads have failed. -- Alexander Motin