| commit | 726c35fa0edf1d9b8a88b73255532e73089aedda | |
| author | Josef Bacik <josef@redhat.com> | |
| Mon, 26 Sep 2011 19:46:06 +0000 (26 15:46 -0400) | ||
| committer | Josef Bacik <josef@redhat.com> | |
| Wed, 19 Oct 2011 19:12:48 +0000 (19 15:12 -0400) | ||
| tree | 5b2c95df5854b5b5829ce5f88e3e807eb4bc8d4a | treesnapshot (tar.gz zip) |
| parent | 1728366efa5ebf48bd2ed544afa8700cd07ba822 | commitdiff |
Btrfs: use the global reserve as a backup for deleting inodes
Xfstests 83 really stresses our ENOSPC since it uses a 100mb fs which ends up
with the mixed block group stuff. Because of this we can run into a situation
where we don't have enough space to delete inodes, or even worse we can't free
the inodes when we next mount the fs which causes the orphan code to lose its
mind. So if we fail to make our reservation, steal from the global reserve.
The global reserve will end up taking up the entire rest of the free space on
the fs in this worst case so there really is no other option. With this patch
test 83 doesn't freak out. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
Xfstests 83 really stresses our ENOSPC since it uses a 100mb fs which ends up
with the mixed block group stuff. Because of this we can run into a situation
where we don't have enough space to delete inodes, or even worse we can't free
the inodes when we next mount the fs which causes the orphan code to lose its
mind. So if we fail to make our reservation, steal from the global reserve.
The global reserve will end up taking up the entire rest of the free space on
the fs in this worst case so there really is no other option. With this patch
test 83 doesn't freak out. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
| fs/btrfs/inode.c | diffblobblamehistory |