Btrfs: remove ASSERT in btrfs_truncate_inode_items
After 76b42abbf7
("Btrfs: fix data loss after truncate when using the
no-holes feature"),
For either NO_HOLES or inline extents, we've set last_size to newsize to
avoid data loss after remount or inode got evicted and read again, thus,
we don't need this check anymore.
Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
1450612797
commit
f95fda8751
|
@ -4603,13 +4603,6 @@ int btrfs_truncate_inode_items(struct btrfs_trans_handle *trans,
|
|||
|
||||
btrfs_free_path(path);
|
||||
|
||||
if (err == 0) {
|
||||
/* only inline file may have last_size != new_size */
|
||||
if (new_size >= fs_info->sectorsize ||
|
||||
new_size > fs_info->max_inline)
|
||||
ASSERT(last_size == new_size);
|
||||
}
|
||||
|
||||
if (be_nice && bytes_deleted > SZ_32M) {
|
||||
unsigned long updates = trans->delayed_ref_updates;
|
||||
if (updates) {
|
||||
|
|
Loading…
Reference in New Issue