| commit | f44d2287d2879f50b921e909b2377d6dcba3e251 | |
| author | Jeff Mahoney <jeffm@suse.com> | |
| Thu, 22 Jun 2017 13:51:47 +0000 (22 09:51 -0400) | ||
| committer | David Sterba <dsterba@suse.com> | |
| Wed, 16 Aug 2017 14:12:05 +0000 (16 16:12 +0200) | ||
| tree | 2d892e37dc250abeb5ea43b0329b38c7f22485df | treesnapshot (tar.gz zip) |
| parent | a7164fa4e055daf6368cb68ed946aa5a362a1a75 | commitdiff |
btrfs: account for pinned bytes in should_alloc_chunk
In a heavy write scenario, we can end up with a large number of pinned bytes.
This can translate into (very) premature ENOSPC because pinned bytes
must be accounted for when allowing a reservation but aren't accounted for
when deciding whether to create a new chunk.
This patch adds the accounting to should_alloc_chunk so that we can
create the chunk.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
In a heavy write scenario, we can end up with a large number of pinned bytes.
This can translate into (very) premature ENOSPC because pinned bytes
must be accounted for when allowing a reservation but aren't accounted for
when deciding whether to create a new chunk.
This patch adds the accounting to should_alloc_chunk so that we can
create the chunk.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
| fs/btrfs/extent-tree.c | diffblobblamehistory |