Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-03-15 Thread David Sterba
On Thu, Mar 15, 2018 at 09:02:28AM +0800, Qu Wenruo wrote: > > The sanity tests are run at module load time, but the new check you are > > adding is a runtime one, so I think the right ifdef is > > CONFIG_BTRFS_DEBUG. > > I'll use CONFIG_BTRFS_DEBUG. > > But the patch is causing rcu problems

Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-03-14 Thread Qu Wenruo
On 2018年03月15日 05:09, David Sterba wrote: > On Tue, Feb 13, 2018 at 09:13:32AM +0800, Qu Wenruo wrote: >> There are reports in mail list, even with latest mainline kernel, btrfs >> can't survive a power loss. >> >> Unlike journal based filesystem, btrfs doesn't use journal for such >> work. (log

Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-03-14 Thread David Sterba
On Tue, Feb 13, 2018 at 09:13:32AM +0800, Qu Wenruo wrote: > There are reports in mail list, even with latest mainline kernel, btrfs > can't survive a power loss. > > Unlike journal based filesystem, btrfs doesn't use journal for such > work. (log tree is an optimization for fsync, not to keep fs

Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-02-13 Thread Nikolay Borisov
On 13.02.2018 13:07, Qu Wenruo wrote: > > > On 2018年02月13日 09:13, Qu Wenruo wrote: >> There are reports in mail list, even with latest mainline kernel, btrfs >> can't survive a power loss. >> >> Unlike journal based filesystem, btrfs doesn't use journal for such >> work. (log tree is an

Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-02-13 Thread Qu Wenruo
On 2018年02月13日 09:13, Qu Wenruo wrote: > There are reports in mail list, even with latest mainline kernel, btrfs > can't survive a power loss. > > Unlike journal based filesystem, btrfs doesn't use journal for such > work. (log tree is an optimization for fsync, not to keep fs healthy) > In

Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-02-13 Thread Qu Wenruo
On 2018年02月13日 15:20, Nikolay Borisov wrote: > > > On 13.02.2018 03:13, Qu Wenruo wrote: >> There are reports in mail list, even with latest mainline kernel, btrfs >> can't survive a power loss. >> >> Unlike journal based filesystem, btrfs doesn't use journal for such >> work. (log tree is an

Re: [PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-02-12 Thread Nikolay Borisov
On 13.02.2018 03:13, Qu Wenruo wrote: > There are reports in mail list, even with latest mainline kernel, btrfs > can't survive a power loss. > > Unlike journal based filesystem, btrfs doesn't use journal for such > work. (log tree is an optimization for fsync, not to keep fs healthy) > In

[PATCH] btrfs: Verify extent allocated by find_free_extent() won't overlap with extents from previous transaction

2018-02-12 Thread Qu Wenruo
There are reports in mail list, even with latest mainline kernel, btrfs can't survive a power loss. Unlike journal based filesystem, btrfs doesn't use journal for such work. (log tree is an optimization for fsync, not to keep fs healthy) In btrfs we use metadata CoW to ensure all tree blocks are