Re: [PATCH 5/5] btrfs: replace: Use ref counts to avoid destroying target device when canceled

2017-03-20 Thread Liu Bo
On Mon, Mar 20, 2017 at 02:30:48PM +0800, Qu Wenruo wrote: > > > At 03/18/2017 10:12 AM, Liu Bo wrote: > > On Fri, Feb 03, 2017 at 04:20:23PM +0800, Qu Wenruo wrote: > > > When dev-replace and scrub are run at the same time, dev-replace can be > > > canceled by scrub. It's quite common for

Re: [PATCH 5/5] btrfs: replace: Use ref counts to avoid destroying target device when canceled

2017-03-20 Thread Qu Wenruo
At 03/18/2017 10:12 AM, Liu Bo wrote: On Fri, Feb 03, 2017 at 04:20:23PM +0800, Qu Wenruo wrote: When dev-replace and scrub are run at the same time, dev-replace can be canceled by scrub. It's quite common for btrfs/069. The backtrace would be like: general protection fault: [#1] SMP

Re: [PATCH 5/5] btrfs: replace: Use ref counts to avoid destroying target device when canceled

2017-03-17 Thread Liu Bo
On Fri, Feb 03, 2017 at 04:20:23PM +0800, Qu Wenruo wrote: > When dev-replace and scrub are run at the same time, dev-replace can be > canceled by scrub. It's quite common for btrfs/069. > > The backtrace would be like: > general protection fault: [#1] SMP > Workqueue: btrfs-endio-raid56

[PATCH 5/5] btrfs: replace: Use ref counts to avoid destroying target device when canceled

2017-02-03 Thread Qu Wenruo
When dev-replace and scrub are run at the same time, dev-replace can be canceled by scrub. It's quite common for btrfs/069. The backtrace would be like: general protection fault: [#1] SMP Workqueue: btrfs-endio-raid56 btrfs_endio_raid56_helper [btrfs] RIP: 0010:[] []