From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f52.google.com ([74.125.82.52]:38428 "EHLO mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752123AbcF3N6q (ORCPT ); Thu, 30 Jun 2016 09:58:46 -0400 Received: by mail-wm0-f52.google.com with SMTP id r201so120116240wme.1 for ; Thu, 30 Jun 2016 06:58:45 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1fb4624c-4a2f-6076-0883-4a7bff395821@oracle.com> References: <1fb4624c-4a2f-6076-0883-4a7bff395821@oracle.com> From: Timofey Titovets Date: Thu, 30 Jun 2016 16:58:04 +0300 Message-ID: Subject: Re: RAID1: if one disk failed, what errors are expected? To: Anand Jain Cc: linux-btrfs Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: 2016-06-30 14:57 GMT+03:00 Anand Jain : > > > Thanks for reporting. > > Right. Application shouldn't notice the EIO. First of all, > we are not stopping IO to the disk which is pulled out. The > below patches 11/13 and 12/13 fixes it. > > [PATCH 11/13] btrfs: introduce device dynamic state transition to offline > or failed > [PATCH 12/13] btrfs: check device for critical errors and mark failed > > > Next, if degraded mount fails, you will also need below patches. > However there are two choices.. > > Patch 1..5/13 are workaround fixes.. > [PATCH 01/13] btrfs: Introduce a new function to check if all chunks a OK > for degraded mount > [PATCH 02/13] btrfs: Do per-chunk check for mount time check > [PATCH 03/13] btrfs: Do per-chunk degraded check for remount > [PATCH 04/13] btrfs: Allow barrier_all_devices to do per-chunk device check > [PATCH 05/13] btrfs: Cleanup num_tolerated_disk_barrier_failures > > OR > > Below RFC patch which has the actual fix (lightly tested), > PATCH 0/2] [RFC] btrfs: create degraded-RAID1 chunks > > Could you please give it a try ? > > Thanks, Anand > Yes, i will, thanks. -- Have a nice day, Timofey.