diff options
author | Josef Bacik <jbacik@fusionio.com> | 2012-10-22 21:43:12 +0200 |
---|---|---|
committer | Chris Mason <chris.mason@fusionio.com> | 2012-10-25 21:50:18 +0200 |
commit | be6aef604920406b348acf3be6e6e8db55696386 (patch) | |
tree | 2d458852fafacb2bad7788311b10b879ba920f40 /fs/btrfs/transaction.c | |
parent | Btrfs: Send: preserve ownership (uid and gid) also for symlinks. (diff) | |
download | linux-be6aef604920406b348acf3be6e6e8db55696386.tar.xz linux-be6aef604920406b348acf3be6e6e8db55696386.zip |
Btrfs: Use btrfs_update_inode_fallback when creating a snapshot
On a really full file system I was getting ENOSPC back from
btrfs_update_inode when trying to update the parent inode when creating a
snapshot. Just use the fallback method so we can update the inode and not
have to worry about having a delayed ref. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to '')
-rw-r--r-- | fs/btrfs/transaction.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c index 77db875b5116..04bbfb1052eb 100644 --- a/fs/btrfs/transaction.c +++ b/fs/btrfs/transaction.c @@ -1200,7 +1200,7 @@ static noinline int create_pending_snapshot(struct btrfs_trans_handle *trans, btrfs_i_size_write(parent_inode, parent_inode->i_size + dentry->d_name.len * 2); parent_inode->i_mtime = parent_inode->i_ctime = CURRENT_TIME; - ret = btrfs_update_inode(trans, parent_root, parent_inode); + ret = btrfs_update_inode_fallback(trans, parent_root, parent_inode); if (ret) btrfs_abort_transaction(trans, root, ret); fail: |