Looks like there's some sort of xattr and Btrfs interaction happening here; but as it only happens with some subvolumes/snapshots not all (but 100% consistent) maybe the kernel version at the time the snapshot was taken is a factor? Anyway git bisect says
# first bad commit: [6c6ef9f26e598fb977f60935e109cd5b266c941a] xattr: Stop calling {get,set,remove}xattr inode operations btrfs-image produces a 159M file. I've updated the bug report https://bugzilla.kernel.org/show_bug.cgi?id=191761 and also adding patch author to cc. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html