From ba8b0289333a70f0d69923fd63350d0b0201b904 Mon Sep 17 00:00:00 2001 From: Josef Bacik Date: Thu, 27 Mar 2014 14:56:51 -0400 Subject: [PATCH] Btrfs: do not reset last_snapshot after relocation This was done to allow NO_COW to continue to be NO_COW after relocation but it is not right. When relocating we will convert blocks to FULL_BACKREF that we relocate. We can leave some of these full backref blocks behind if they are not cow'ed out during the relocation, like if we fail the relocation with ENOSPC and then just drop the reloc tree. Then when we go to cow the block again we won't lookup the extent flags because we won't think there has been a snapshot recently which means we will do our normal ref drop thing instead of adding back a tree ref and dropping the shared ref. This will cause btrfs_free_extent to blow up because it can't find the ref we are trying to free. This was found with my ref verifying tool. Thanks, Signed-off-by: Josef Bacik Signed-off-by: Chris Mason --- Reading git-format-patch failed