2016-06-30 14:57 GMT+03:00 Anand Jain <[email protected]>: > > > 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. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
