Searched hist:be6aef604920406b348acf3be6e6e8db55696386 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/btrfs/ |
| H A D | transaction.c | diff be6aef604920406b348acf3be6e6e8db55696386 Mon Oct 22 14:43:12 CDT 2012 Josef Bacik <jbacik@fusionio.com> 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>
|
| H A D | ctree.h | diff be6aef604920406b348acf3be6e6e8db55696386 Mon Oct 22 14:43:12 CDT 2012 Josef Bacik <jbacik@fusionio.com> 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>
|
| H A D | inode.c | diff be6aef604920406b348acf3be6e6e8db55696386 Mon Oct 22 14:43:12 CDT 2012 Josef Bacik <jbacik@fusionio.com> 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>
|