Re: [PATCH v5 00/13] Introduce device state 'failed', spare device and auto replace

2016-05-01 Thread Anand Jain
Thanks! for report. Sequense was: 1) create FS (RAID5), mount, write 40 MB file, sync 2) detach drive 3) start replace detached (but still not closed) drive by another 4) touch mount point, call 'btrfs fi sync' (I use udev script to initiate write immediately after drive removal) 4) ->

Re: [PATCH v5 00/13] Introduce device state 'failed', spare device and auto replace

2016-04-28 Thread Yauhen Kharuzhy
On Mon, Apr 18, 2016 at 07:31:31PM +0800, Anand Jain wrote: > Thanks for various comments, tests and feedback. > > > Changelog: > - > > v4->v5: > Kernel: > a. Originally we had bugs as fixed in the patches below > [PATCH] btrfs: s_bdev is not null after missing replace >

Re: [PATCH v5 00/13] Introduce device state 'failed', spare device and auto replace

2016-04-25 Thread Yauhen Kharuzhy
On Mon, Apr 18, 2016 at 07:31:31PM +0800, Anand Jain wrote: > Thanks for various comments, tests and feedback. Seems working good for me. -- Yauhen Kharuzhy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More

[PATCH v5 00/13] Introduce device state 'failed', spare device and auto replace

2016-04-18 Thread Anand Jain
Thanks for various comments, tests and feedback. Background: Spare device and Auto replace: Spare device is predominately used to mitigate or narrow the time window of a degraded raid mode, as because during which any further disk failure would lead to a catastrophic data loss. Data center