On Thu, Jun 22, 2017 at 09:51:47AM -0400, [email protected] wrote: > From: Jeff Mahoney <[email protected]> > > 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 <[email protected]>
I'm adding the two patches to for-next. More reviews welcome. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
