On Mon, Mar 23, 2015 at 8:35 AM, Chris Mason <[email protected]> wrote:
On Mon, Mar 23, 2015 at 8:19 AM, Tomasz Chmielewski <[email protected]>
wrote:
Got this with 4.0.0-rc5 when doing a degraded mount:
Do you get this every time, even after going back to rc4?
It should be caused by this commit, but I really don't get how. I'll
dig deeper, but if you can trigger this consistently I'd love to hear
if reverting this commit helps.
commit ea526d18990018f224e5734748975bea1824545f
Author: Josef Bacik <[email protected]>
Date: Fri Mar 13 16:40:45 2015 -0400
Btrfs: fix ASSERT(list_empty(&cur_trans->dirty_bgs_list)
To test things, you'll need to revert this one before the ASSERT fix:
commit dcdf7f6ddba006f3482ebee73dfa6b75aec5f07b
Author: Josef Bacik <[email protected]>
Date: Mon Mar 2 16:37:31 2015 -0500
Btrfs: prepare block group cache before writing
Writing the block group cache will modify the extent tree quite a
bit because it
truncates the old space cache and pre-allocates new stuff. To try
and cut down
on the churn lets do the setup dance first, then later on hopefully
we can avoid
looping with newly dirtied roots. Thanks,
Signed-off-by: Josef Bacik <[email protected]>
--
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
